Replies: 1 comment 1 reply
-
You are definitly right. The features already described in the
When feature types are missing you can add them. I agree that it can be laborious but I didn't find any better solution to make AGAT universal (working with all cases) without any minimal user input. I consider it as semi-automated. The idea is to generate a proper
There is currently no automated way. I would run AGAT once to see what it says (it will list/inform what are the feature types contained within the file and tell you which one are missing in the |
Beta Was this translation helpful? Give feedback.
-
From my experience testing AGAT, it appears critical to have a representation in the feature_levels.yaml file that closely matches the hierarchy in the GFF file being handled, otherwise unintended fixes may be introduced by AGAT. The process of updating the feature_levels.yaml file can be quite laborious when the GFF file contains a lot of feature types with a complex graph.
One such example is the SGD reference GFF, which has a combination of RNA and non-RNA features, self-referencing feature types, feature types with multiple parent types, or leaf feature types pointing directly to root feature types (here is the corresponding graph).
Do you have a recommended way to automate the process of generating a good feature_levels.yaml file or is it something on the roadmap?
Beta Was this translation helpful? Give feedback.
All reactions