Project

General

Profile

Actions
Copy link

Bug #1806

closed

rpn in clusterParamsForm.inc need to be smaller than ppn

Added by Anchi Cheng over 12 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
High
Assignee:
Anchi Cheng
Category:
Web interface
Target version:
Appion/Leginon 3.2
Start date:
05/16/2012
Due date:
% Done:

0%

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

Description

rpn x nodes will be the total number of recon threads that runs. It could not be run if there are not enough processors reserved by ppn x nodes.

I tried to add a validation. However, user may decide to increase ppn to reserve only nodes with more processors and keep rpn the same. However, validator still thinks that the maxvalue is the previous value.

For example, gupy default ppn=4 rpn=8 if I forget to change these, the addValidation('rpn',"maxvalue=".$ppn); creates an error that I can not correct this by changing to ppn=8.

This is the same problem that I found in Carmen's eman_recon job on goby. We can do a work around by defaulting ppn to maxppn.

Actions
Copy link
 #1

Updated by Amber Herold over 10 years ago

  • Status changed from Assigned to In Code Review
  • Assignee changed from Amber Herold to Anchi Cheng
  • Target version changed from Appion/Leginon 2.2.0 to Appion/Leginon 3.2
  • Affected Version changed from Appion/Leginon 2.2.0 (trunk) to Appion/Leginon 2.2.0
Actions
Copy link
 #2

Updated by Anchi Cheng about 9 years ago

  • Status changed from In Code Review to Closed
Actions
Copy link

Also available in: Atom PDF