Project

General

Profile

Actions

Bug #2911

open

DoG Picking test mode

Added by Emily Greene over 10 years ago. Updated almost 9 years ago.

Status:
Merge
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
08/21/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
Appion/Leginon 3.1.0
Show in known bugs:
No
Workaround:

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


Related issues 3 (2 open1 closed)

Related to Appion - Bug #2138: Particle picking "Test these settings on image" causes problemsNew11/09/2012

Actions
Related to Appion - Bug #3765: commit doesn't uncheck when testing image in dogpickerClosedSargis Dallakyan11/12/2015

Actions
Related to Appion - Bug #3837: Refresh the web form to see not quite finished test results causes submitted job to resubmitAssignedAnchi Cheng12/16/2015

Actions
Actions #1

Updated by Amber Herold over 10 years ago

  • Status changed from New to Assigned
  • Assignee set to Sargis Dallakyan
Actions #2

Updated by Sargis Dallakyan about 10 years ago

  • Related to Bug #2138: Particle picking "Test these settings on image" causes problems added
Actions #3

Updated by Sargis Dallakyan about 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.

Actions #4

Updated by Amber Herold about 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?

Actions #5

Updated by Anchi Cheng almost 9 years ago

  • Related to Bug #3765: commit doesn't uncheck when testing image in dogpicker added
Actions #6

Updated by Anchi Cheng almost 9 years ago

  • Related to Bug #3837: Refresh the web form to see not quite finished test results causes submitted job to resubmit added
Actions #7

Updated by Anchi Cheng almost 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".

Actions #8

Updated by Anchi Cheng almost 9 years ago

  • Status changed from In Test to Merge
Actions

Also available in: Atom PDF