This page lists potential inconsistencies in the database, uncovered by automated data-validation routines. These may be mismatch between the format of the data and the FPbase "convention", inconsistencies with external databases (such as GenBank), or inconsistencies between different fields in the database that capture similar information (switch type and transitions, or lineage mutations and sequence). Not all items are necessarily problematic, but this is a good place to begin looking for things to clean up. If you'd rather fill in missing information in the database, start here.
Either a mutation string problem, misalignment, or doesn't yield the child sequence.
GGvT: GdT + M1M does not match the current GGvT sequence (Δ: *0_M1insMVSKGEEVIKEFMRFKVRMEGSMNGHEFEIEGEGEGRPYEGTQTAKLKVTKGGPLPFAWDILSPLLMYGSKMYVKHPADIPDYKKLSFPEGFKWVRVMNFEDGGLVTATQDSSLQDGTLIYEVKMRGTNFPPDGPVMQKKTMGWEASTERLYPRDGVLKGEIHQALKLKDGGHYLVEFKTIYMAKKPVQLPGYYYVDTKLDITSHNEDYTRVEQYERSEGRHHLFLYDMDELYKGSTGSGSSGP)
sfCherry: mCherry + R41H/K97T/R130L/S152T/K167N/N201D does not match the current sfCherry sequence (Δ: V2_G5del/M231_K236del)
sfCherry2: sfCherry + E118Q/T128I/G220A does not match the current sfCherry2 sequence (Δ: M1del/G225_G226del)
sfCherry3C: sfCherry2 + K45R/G52D/T106A/K182R/N194D does not match the current sfCherry3C sequence (Δ: *0_E1insM)
pH-tdGFP: Superfolder GFP + N149Y/Q204H does not match the current pH-tdGFP sequence (Δ: E6_L7insLFTGVVPILVELDGDVNGHKFSVRGEGEGDATNGKLTLKFICTTGKLPVPWPTLVTTLTYGVQCFSRYPDHMKRHDFFKSAMPEGYVQERTISFKDDGTYKTRAEVKFEGDTLVNRIELKGIDFKEDGNILGHKLEYNFNSHYVYITADKQKNGIKANFKIRHNVEDGSVQLADHYQQNTPIGDGPVLLPDNHYLSTHSVLSKDPNEKRDHMVLLEFVTAAGITHGHGTGSTGSGSSGTASSEDNNMA)
spGFP 11: Superfolder GFP + L221H/F223Y/T225N does not match the current spGFP 11 sequence (Δ: M1_K214del/H231_K238del)
esGFP: Superfolder GFP + L42I/F46L/L64C/T65G/S72A/Y106F/L119T/E124K/N149K/L194R/L207I/S208L/K209E/L221H does not match the current esGFP sequence (Δ: T119I)
pHluorin2: pHluorin, ratiometric + F64L does not match the current pHluorin2 sequence (Δ: R80Q/T161I/A163V/G175S/L220F)
TagRFP658: TagRFP657 + N71D/Q111H/A150T/K203E/K207N does not match the current TagRFP658 sequence (Δ: T6K/T177I/S226T)
FusionRed-MQV: FusionRed-M + M42Q/C159V does not match the current FusionRed-MQV sequence (Δ: M171L/L175M)
miRFP2: miRFP + D16S/V66I/P85L/P127S/A155V/Q175R/E211V/S222T/E300V does not match the current miRFP2 sequence (Δ: R22H)
eYGPdp: YGFPdp + K69E/M205I does not match the current eYGPdp sequence (Δ: C134W)
Sequences that do not match GenBank
These sequences do not exactly match the sequence for the corresponding genbank ID. Sometimes this is just because the genbank sequence has slight N/C terminal differences, or perhaps a His tag. Sometimes it indicates a problem with our sequence, and sometimes Genbank is wrong! The gray text shows the mutation from the FPbase sequence to the Genbank sequence. N- and C- terminal mismatches are less of a concern than internal single point mutations. If you uncover an inconsistency in the literature (e.g. between the paper and the GenBank sequence) please let us know!
Proteins whose states/transitions are inconsistent with their switch type
This may indicate a mis-categorized switch type, or it may indicated that the states and transitions of the protein are not yet completed or accurate. See the documentation for a review on how FPbase categorizes switching types.