Bug #1090
closedExtra dmf command in get files from dmf (after EMAN run on garibaldi) that is not needed
0%
Description
I don't think we need the dmf command:
dmf get /home/bcarr/appion/10may20c/recon/emanrecon3/*.job /ami/data15/appion/10may20c/recon/emanrecon3/.
in the get files form dmf after an EMAN run.
It is not a problem but just should be removed so as not to confuse people. Right now is just generates and error and you can continue.
Updated by Anchi Cheng almost 14 years ago
Why not? The copying is used to ensure that the job file is archived in the final destination. Especially if you modified the job file on the cluster. The path to get the job file is probably set incorrectly, therefore the error. That is probably what need to be fixed.
Updated by Bridget Carragher almost 14 years ago
Yes I agree we need it but I think it gets scooped up with the other files? If not then yes need to fix the path.
Updated by Amber Herold almost 14 years ago
- Assignee set to Dmitry Lyumkis
- Target version set to Appion/Leginon 2.2.0
- Deliverable set to 2.2 Bug Reduction
Dmitry and Christopher are tasked with deciding on a single best practice for processing on Garibaldi, implementing and documenting.
Updated by Amber Herold almost 14 years ago
From Lauren:
The "Get files from DMF" button shows up on the checkRefineJobs.php page even when the job was submitted to Guppy or Goby. This button should only exist when running on Garibaldi because Garibaldi is the only one that requires transfer from DMF. For now we can just ignore this button and go straight to "Upload EMAN results", but this should be fixed to avoid confusion.
Updated by Amber Herold over 13 years ago
- Status changed from New to Assigned
- Assignee changed from Dmitry Lyumkis to Amber Herold
Updated by Anchi Cheng over 13 years ago
As a note, I found it still needed (just the tar expanding part) when it is run from garibaldi because we didn't put the tar expansion in upload and the upload web gui won't start without it decompressed.
Updated by Amber Herold almost 13 years ago
- Status changed from Assigned to Won't Fix or Won't Do
This is no longer relevant for 2.2 and I don't think we should address this in previous versions.