You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I understand, the current SPARQL checks are oriented towards GAF-y use cases. We will increasingly want to have both "hot" reports (in Noctua, etc.) and pipeline reports for GO-CAM use cases.
This ticket is to start trying to get some of these into the pipeline to help catch issues such as geneontology/noctua#570 as early as possible (damage mitigation).
Closing would be at least getting a runner working, with templated/PR-able arguments, and the query to catch the above as one of them.
As I understand, the current SPARQL checks are oriented towards GAF-y use cases. We will increasingly want to have both "hot" reports (in Noctua, etc.) and pipeline reports for GO-CAM use cases.
This ticket is to start trying to get some of these into the pipeline to help catch issues such as geneontology/noctua#570 as early as possible (damage mitigation).
Closing would be at least getting a runner working, with templated/PR-able arguments, and the query to catch the above as one of them.
Tagging @dougli1sqrd @lpalbou
The text was updated successfully, but these errors were encountered: