Using Sexed Sires
4 min
customers who do not use naab codes can use the enhanced sexed sire feature in dairycomp to designate a sire as sexed female, sexed male, and sexed and unsexed beef sires how does this help me? this primarily helps customers outside of the us, particularly in europe, where naab codes are not available in the us and various other countries, naab codes are used to designate sexed semen for example, code 11h123 is an unsexed sire and code 511h123 is the sexed variant both codes refer to the same bull, just different semen straw options this works quite well when designating sorting status for both dairy and beef bulls however, not every country uses naab codes, for example germany, italy, and the uk so you would need a way to designate any sire as sexed, without relying on naab codes for example, germany uses dhv codes for sires, where sires are 6 digit numbers like 409123 , but there may also be a sexed semen variant of 409123 in this case, there would be no way to know which sire number is sexed, so you can used the sexed sire feature in dairycomp to designate your sires as sexed female, sexed male, and sexed and unsexed beef sires note this feature is mainly for non‑us herds, where naab codes are not available in the us, it is always, highly recommend that you use naab codes for sire entries the short names, iso tags, breed, etc are still available, and the short name, breed, stud, and sexed code are automatically populated for any sire defined with a naab code to help clarify the benefit of using naab codes, the ability to edit breed and stud codes from the sire edit screen in alter\8 has been removed see the topics below to learn more about using sexed sires how to designate a sexed sire the simplest method is to add s to any sire name to designate it as sexed when entering it into dairycomp for example 12345 is not sexed and 12345 s is sexed the command for the sexed sire would look like this enter sid=12345 s with this enabled (which is the default for most of europe and canada), bred will offer a list of the available sires, and they can be selected by entering all or part of the short name with sexed sires, you can select an alternate suffix, and a new sire can be added during the enter process (as shown in the example command above) if you enter the sire nexus, that is dhv code 509877, you can optionally select the sexed variant, which would store 509877 s in the sire table (the name is still nexus, but displayed as nexus s ) this is what the cowcard would look like if bred to sire nexus with the sexed code selected as "sexed female" the more advanced method is to edit the sire in the alter 8 sires configuration window see editing sires in the alter8 sires configuration docid\ xcyasaqbuarogpdhjar3 ]below for instructions, as well as some cautions, when using this advanced option editing sires in the alter8 sires configuration this sexed sire feature targets herds that do not always use naab codes; it does not apply to naab‑coded sires in previous dairycomp versions before the sexed sire feature existed, the system would decode the naab code and automatically extract the breed, stud, and sexed code this behavior does not change however, if you attempt to add a sexed code suffix to a naab‑coded sire in the current version of dairycomp, it will be stripped away and ignored for example, the naab‑coded sire 501h7153 has an obvious stud code of 501 and a breed of h, with a sexed code of s (which is determined by the stud code that is looked up the within dairycomp list that is populated via the published naab list https //www naab css org/naab marketing codes https //www naab css org/naab marketing codes ) \<font color="#f97316">important\</font> alter8 rejects the s suffix if you attempt to add it to a naab‑coded sire the example below shows the alter\8 sire configuration window it shows the 501h7153 naab code entered with a s after clicking ok, the suffix is ignored and not saved this is also true if entering a bred event using the 501h7153 s naab code; the s suffix is dropped by contrast, alter 8 allows the s suffix when you add it to a non‑naab‑coded sire the example below shows alter\8 while editing a non naab coded sire in a non us herd with this option, you are able to select from the sire code suffix list to designate the sexed sire displaying sexed codes as items normally, type 190 "sire items" has been used to show the various parts of a sire that can be extracted as items like every item, there are two operators ("ops"), and for type 190 the first operator is the sire item to be referenced, usually sid, and could also be lsir, sirc, etc the second operator (op2) designates the sire value to be displayed for the item specified in the first operator example — item type 190 for sire 29h19625 \<font color="#f3f4f6">op2\</font> \<font color="#f3f4f6">example\</font> \<font color="#f3f4f6">description\</font> 0 or 2 29h19625 default field, naab where available 1 laker sire name 3 840003209481114 iso value, using user preferred display option 4 h breed 5 29 stud code 6 ns or ai based on stud code, not common, specific to some eu countries 7 offspring gender s, m, b, p, or qsee sexed sire items docid\ xcyasaqbuarogpdhjar3 below for details 8 840003209481114 iso as numeric 9 us003209481114 iso as alpha 2 country 10 usa003209481114 iso as alpha 3 country 11 abs stud name sexed sire items if you create a type 190 item with an op2 of 7, it is displayed as a character, with this table \<font color="#f3f4f6">code\</font> \<font color="#f3f4f6">meaning\</font> blank unsexed s sexed female m sexed male b unsexed beef r sexed female beef q sexed male beef sexed sire items can be selected in the command line see the table below for examples \<font color="#f3f4f6">name\</font> \<font color="#f3f4f6">type\</font> \<font color="#f3f4f6">op1\</font> \<font color="#f3f4f6">op2\</font> \<font color="#f3f4f6">meaning\</font> \<font color="#f3f4f6">example\</font> sidsx 190 sid 7 sexed coded of animal sire show id sidsx for sidsx=s show daughters of sexed sires lsirx 190 lsir 7 sexed code of last sire used show id lsirx for lsirx=s show animals bred last to a sexed sire show id lsirx for lsirx=b show animals bred last to a beef sire sircx 190 sirc 7 sexed code of conception sire show id sircx for sircx=s show animals pregnant to a sexed sire show id sircx for sircx=b show animals pregnant to a beef sire the example below is from a german herd, with shortnames enabled as displayed in the example above, sire 12345 is unsexed, but there is also a sire entered as 12345 s, which set sire sexed code to sexed female, and is displayed as s, which represents the primary goal for this feature logic for showing the sexed code used the following priority if the sire name is a naab code, that determines the code, based on the stud in the naab, which is used to set the sexed indicator this remains unchanged and naab takes precedence as you cannot designate sexed codes for naab sires also, you cannot enter 7h1234 s enter as 7h1234 will be displayed as the naab code and dairycomp will ignore the attempt to designate the sexed code if the internal sexed code was set via entry such as 12345 s , or in alter8 editing, it is used for the indicator example commands the example below shows the breakdown of conception sires by sexed code as displayed, 16% of the existing pregnancies are to beef bulls and 17% are to sexed female sires bredsum can be summarized by sexed codes as well use the option displayed below or the bredsum\\ command how sexed sires are stored in the sire table a sexed‑coded sire exists as a separate entity in the sire table 12345 and 12345 s are both in the sire table, at different indexes however, they still represent the same genetic animal, and when dairycomp updates data from the sire table, both 12345 and 12345 s will be updated with the same data they have the same name, iso tag, etc