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.
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!
Everything should start with Met. Cross check sequences with original publication and clean up.
Usually, these sequences were pulled from PDB. Cross-check with originally publication, and remove His tag and any C- N- terminal linkers
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.
Proteins whose names (or publication titles) suggest that they may be switchable/convertable, but have only a single fluorescent state.