Open anitacaron opened 2 months ago
measure (on the base file, which the result is not being used)
I am wondering if this is a good thing - that it is not being used. Does it mean the file metrics we report in the dashboard all use the whole ontology?
Does it mean the file metrics we report in the dashboard all use the whole ontology?
Yes, only in cases where the base was generated.
The simple solution would be to change the order of the chain.
make_base
is true)If the remove command is not run when the base file is available, then ok, I guess we can do that. Its a bit weird for some ontologies that dont have a base, like application ontologies, to show metrics of the base (think OMO), but I am not opposed to try this, and see how it looks!
There's a function to generate a ROBOT command that has many commands in a chain, which may be unnecessary. It can be time-consuming and memory-consuming for large ontologies, e.g., NCBITaxon, PCL, or NCIT.
The chain commands are:
I would suggest removing, at least the second measure.
To illustrate, this is the current ROBOT command for NCBITaxon:
https://github.com/OBOFoundry/OBO-Dashboard/blob/e39cde99db31b0b32ac1a064f12286eb19da1143/util/lib.py#L343-L377