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