Conversation
cax/cax.json
Outdated
| "download_options": ["midway-login1"], | ||
| "pax_processing_versions": [ | ||
| "v4.10.0" | ||
| "v4.10.2" |
There was a problem hiding this comment.
won't this trigger a reprocessing?
|
Anyways, added a few comments. Some big things (check main.py). One key thing: the data type is processed and status is transferred. That means good. If you manually change verifying to transferred, then you have no idea if the data is any good... that's why we have checksumming. |
…rmissions every 60min
…rmissions every 60min
…rmissions every 60min
cax/config.py
Outdated
| def pax_deploy_directories(host, pax_version): | ||
| PAX_DEPLOY_DIRS = { | ||
| 'midway-login1' : '/project/lgrandi/deployHQ/pax', | ||
| 'tegner-login-1': '/afs/pdc.kth.se/projects/xenon/software/pax/pax_'+pax_version |
There was a problem hiding this comment.
Why do you need to specify pax version here? You should have one anaconda setup that has different environments for different pax versions. That's why this wasn't a function.
There was a problem hiding this comment.
I think my aim was to specify to the actual pax version in the path. But this is not important. Changed it back
|
Looks good, added some comments. Not far from merging. Need to resolve some merge conflcits. |
…om SetPermissions
|
Can you merge with master? |
|
Also, @XeBoris when you get a chance, can you please update the README with all the latest features/options? |
3 participants
I added some features to cax-status which helps to identify the status of files/folder of our data in the data base. I started to use this tool as replacement for actual using the web interface to the run data base
I tested cax-process manually. Furthermore I added parser options to make life more easier in case someone wants to use cax-process. Batch processing should work too.