Re: conversation with @matentzn on April 1:
We would like to be able to use alternative versions of PHENIO in automate-pheno-comparisons for evaluation, e.g., PHENIO with development version of Upheno.
These should be run in a manner identical to that as that in the current Jenkins pipeline, with the following modifications:
- Provide a flag to use an alternative PHENIO source.
- If the flag is set, retrieve the alternative PHENIO from a specified URL.
This URL will need to point to a gzipped semsql version of PHENIO, identical in format to that of https://s3.amazonaws.com/bbop-sqlite/phenio.db.gz .
The alternative PHENIO version will need to have its own versionIRI distinct from that of the "production" build.
- Upload the results to KG-Hub in their own directory, named using the versionIRI.
Re: conversation with @matentzn on April 1:
We would like to be able to use alternative versions of PHENIO in automate-pheno-comparisons for evaluation, e.g., PHENIO with development version of Upheno.
These should be run in a manner identical to that as that in the current Jenkins pipeline, with the following modifications:
This URL will need to point to a gzipped semsql version of PHENIO, identical in format to that of https://s3.amazonaws.com/bbop-sqlite/phenio.db.gz .
The alternative PHENIO version will need to have its own versionIRI distinct from that of the "production" build.