Due to a naming clash that goes back many years, two different alleles of nompC, with contrasting molecular lesions, were named nompC[3]. Thanks to user input, we have been able to disambiguate these two alleles. They are now called nompC[3] and nompC[b19]. The nompC[3] allele was generated in the Zuker lab by EMS (FBrf0127378). The nompC[b19] allele was made by Szidonya and Reuter (FBrf0047784) and published in 1988 as jf24[b19]. Allele jf24[b19] was renamed in Lindsley and Zimm 1992 (p. 353) as l(2)25Dc[3]. Allele l(2)25Dc[3] subsequently became nompC[3] based on a foot note in Kernan et al., 1994 (FBrf0073546) identifying l(2)25Dc as nompC. The references and data for jf24[b19]/l(2)25Dc[3]/nompC[3] have now been split from the nompC[3] FlyBase record and are associated with allele nompC[b19].
Due to a naming clash that goes back many years, two different alleles of nompC, with contrasting molecular lesions, were named nompC[3]. Thanks to user input, we have been able to disambiguate these two alleles. They are now called nompC[3] and nompC[b19]. The nompC[3] allele was generated in the Zuker lab by EMS (FBrf0127378). The nompC[b19] allele was made by Szidonya and Reuter (FBrf0047784) and published in 1988 as jf24[b19]. Allele jf24[b19] was renamed in Lindsley and Zimm 1992 (p. 353) as l(2)25Dc[3]. Allele l(2)25Dc[3] subsequently became nompC[3] based on a foot note in Kernan et al., 1994 (FBrf0073546) identifying l(2)25Dc as nompC. The references and data for jf24[b19]/l(2)25Dc[3]/nompC[3] have now been split from the nompC[3] FlyBase record and are associated with allele nompC[b19].