Bug #575
closedGet files from DMF wants to transfer coran results even though it does not exist
100%
Description
This generates three annoying error messages.
Updated by Anchi Cheng almost 14 years ago
- Status changed from Assigned to In Code Review
- Assignee changed from Anchi Cheng to Eric Hou
- % Done changed from 0 to 100
r14198 fixes this in the branch. merged and committed to trunk as r14199
Updated by Eric Hou almost 14 years ago
- Status changed from In Code Review to In Test
- Assignee changed from Eric Hou to Amber Herold
Updated by Amber Herold almost 14 years ago
- Assignee changed from Amber Herold to Anchi Cheng
Anchi, can you please provide a test procedure?
Updated by Anchi Cheng almost 14 years ago
- Assignee changed from Anchi Cheng to Amber Herold
Testing
1. run a one refine cycle eman reconstruction job on garibaldi that does not use coran feature.
2. when the job is completed, appion will assign its status to awaiting to upload
3. At this point, the a few files are saved in dmf under your dmf home directory
4. Click on Get file from DMF will pop up a window. None of the lines should contain the word coran.
see http://cronus3.scripps.edu/~acheng/dev/myamiweb/processing/checkRefineJobs.php?expId=7550 for an example (emanrecon8)
5. run a similar job with coran feature on and follow step 2-5. This time there should contain
three lines for transfering coran results.
Updated by Amber Herold almost 14 years ago
- Assignee changed from Amber Herold to Alex Kadokura
Alex, could you test this...I need to get set up on the cluster before I can test it.
Updated by Anchi Cheng almost 14 years ago
- Status changed from In Test to Closed
- Assignee changed from Alex Kadokura to Anchi Cheng
- Affected Version set to Appion/Leginon 2.0.1
tested and found one echo of "dmf ls coran.tar.gz" removed in r14388 in trunk and r14387 in branch