Bug #2911
openDoG Picking test mode
0%
Description
When trying to test out DoG picker settings, it sometimes requires refreshing the webpage 10-12 times (or it just doesn't work), but every once in a while it works the first time. It is at this point faster to just start a particle picking run and see the results for the first few micrographs. Attached is an image of the error message.
(I tried to look if this was a previous issue, but I'm not that good with Redmine, so let me know if this is part of a different thread or if I need more information)
Files
Updated by Amber Herold over 10 years ago
- Status changed from New to Assigned
- Assignee set to Sargis Dallakyan
Updated by Sargis Dallakyan over 10 years ago
- Related to Bug #2138: Particle picking "Test these settings on image" causes problems added
Updated by Sargis Dallakyan over 10 years ago
- Status changed from Assigned to In Test
- Assignee changed from Sargis Dallakyan to Emily Greene
Commited r18541 to fix this bug. Instead of running test jobs on the head node, now they are submitted to cluster nodes through runJob.py. Also, r18542 changed runDogPicker.php so that test jobs results are commited to database by default.
Updated by Amber Herold over 10 years ago
Sargis,
It sounds like now test runs will behave just like a regular run, except that only one image is processed. So each test is stored under a new run name and appears in the pipeline as a completed run. The user will need to click on the appropriate run in the completed runs page to view the result. Correct?
Updated by Anchi Cheng about 9 years ago
- Related to Bug #3765: commit doesn't uncheck when testing image in dogpicker added
Updated by Anchi Cheng about 9 years ago
- Related to Bug #3837: Refresh the web form to see not quite finished test results causes submitted job to resubmit added
Updated by Anchi Cheng about 9 years ago
- Assignee changed from Emily Greene to Anchi Cheng
r18542 was reverted by r19368 because of issue #3765
The root of this problem is that refreshing the page, which keeps all $_POST, causes the job to be resubmitted or rerun whether it is on the head node or through qsub. Keeping all $_POST except the call to submit can only be achieved if $_POST['process'] is overwritten through a different input value activated by CLICKING another button, such as "Just Show Command" or something else we dedicate for the purpose.
Open Issue #3765 to make a button called "Refresh Test Results".