Open cmungall opened 2 years ago
Add to tech board @shawntanzk
Thanks a lot @cmungall
Should these antislims be created or generated? i.e. how will we know that fin/limb should be excluded from human-view? Manual curation?
From tech group meeting: we won't act on this ticket yet because we need to figure out how to implement the GAP filling over existential (Anitas comment edited by @matentzn )
From tech group meeting: we won't act on this ticket yet because we need to figure out how to implement the GAP filling over existential (Anita's comment edited by @matentzn )
@anitacaron - we should discuss progress on this (as tested on scAtlas)
This issue has not seen any activity in the past 6 months; it will be closed automatically one year from now if no action is taken.
We can close this issue when the new ROBOT subset command is released.
Are you sure? Robot subset will not allow removing "paw or hand” type classes without an anti slim approach. Maybe I am wrong though.
This issue has not seen any activity in the past 6 months; it will be closed automatically one year from now if no action is taken.
Add antislims that can be applied that should be excluded from specific releases
E.g.
These are formally weaker than never-in-taxon. In particular, they are safe for intermediate classes and they are safe for classes that may be excluded due to being "too specific" for a use case without worrying about whether there is an existential linking to it
Examples
The antislim would be applied after logic-based subset extraction (regardless of which logic-based strategy is used here: #2137)
The relevant owltools command is
--extract-ontology-subset
HOWEVER, this only supports specifying a positive subset. Options
Assuming 1, the command would be
owltools uberon-post-logic-filtering-euarch.owl --extract-ontology-subset -s include_in_euarch_release -o euarch.owl
Make sure that relax is first executed.
Some curation guidelines for using the subset