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