caro fu-AO jenkins jobs should generate merged OWL file

[dosumis]

OWL file needed for checking reasons for unsatisfiability.

[cmungall]

Not sure what you mean...

[dosumis]

Would like an owl file I can use to trace the reasons for unstatisfiable classes for xao-caro, zfa-caro jenkins jobs. (looked for one in the workspace, but didn't see anything obvious).
cheers,
David

[cmungall]

In theory you should be good to go with the basic caro checkout from github: the bridge files contain imports. The AO is always pulled over the wire rather than having a copy locally. The AO-caro jobs just pull from the caro github, not the external AO.

Hmm, this is not ideal as the checks are immediately downstream of the build-AO jobs, and the owl won't immediately visible from the AO editor's latest edits. Need to do something more complicated it seems...

What would be useful would be a dump of the module created containing the unsats. I'll check with @hdietze how this can be done.

[dosumis]

What would be useful would be a dump of the module created containing the unsats.

That would be perfect.