Changes between Version 1 and Version 2 of Pantasks_FAQ
- Timestamp:
- May 14, 2009, 1:46:33 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Pantasks_FAQ
v1 v2 4 4 ==== How do I start pantasks? ==== 5 5 start up pantasks from a terminal window 6 {{{ 6 7 > pantasks 7 8 … … 10 11 load some pantasks commands 11 12 pantasks: module pantasks.pro 12 13 }}} 13 14 or, if you have a modified pantasks.pro file 15 {{{ 14 16 pantasks: input /home/username/pantasks/pantasks.pro 15 17 }}} 16 18 After loading the pantasks.pro file, you can add a database easily: 19 {{{ 17 20 pantasks: add.database mydatabase 18 21 }}} 19 22 If you don't add a database, pantasks will use the one declared in your .ipprc file. 20 23 … … 27 30 28 31 Connect to a controller host 32 {{{ 29 33 pantasks: controller host add myhost 30 34 }}} 31 35 Check the controller host status (NOTE: This will sometimes return no info, even when there are active hosts): 36 {{{ 32 37 pantasks: controller status 33 38 }}} 34 39 Check the processing status: 40 {{{ 35 41 pantasks: status 36 42 }}} 37 43 For additional timing details: 44 {{{ 38 45 pantasks: status -taskstats 39 46 40 47 Start processing: 41 48 pantasks: run 42 49 }}} 43 50 Stop adding new processes, but finish out the queue : 51 {{{ 44 52 pantasks: stop 45 53 }}} 46 54 Stop processes right now : 55 {{{ 47 56 pantasks: halt 48 57 }}} 49 58 Exit pantasks : 59 {{{ 50 60 pantasks: exit 51 61 }}} 52 62 53 63 ==== How do I get more verbose output from pantasks? ==== 54 64 65 {{{ 55 66 pantasks: $VERBOSE = 1 56 67 }}} 57 68 Raise the number above 1 for more and more verbosity. 58 69 … … 64 75 In your .ipprc file, you may have defined the path to your configuration directory with something like this: 65 76 77 {{{ 66 78 PATH STR /path/to/my/system/level/ippconfig 67 79 }}} 68 80 So in your system.config file you can define the directory for your GPC1 camera.config file with this line: 69 81 82 {{{ 70 83 CAMERAS METADATA 71 84 GPC1 STR gpc1/camera.config … … 73 86 74 87 so when you run any script that needs to reference the GPC1 camera it will look 75 * first in the current directory for ./gpc1/camera.config88 }}} * first in the current directory for ./gpc1/camera.config 76 89 * next in the directory defined by your .ipprc PATH variable (in this case /path/to/my/system/level/ippconfig/gpc1/camera.config) 77 90 … … 83 96 84 97 * First, check that you can ssh from the machine on which you are running pantasks to the node without being prompted for a password and without errors reading your shell startup file (.bashrc, .cshrc, .profile, .login and the like): 98 {{{ 85 99 * Try "ssh myhost" 86 100 * If you're prompted for a password, then you need to set up ssh keys, and/or check your ssh configuration. 87 * Second, check that you can start up 'pclient' over an ssh connection. For that to work, you need to run 'psconfig ipp-2.6.1' (or whatever the IPP version is called on your system) in your startup file. 101 }}} * Second, check that you can start up 'pclient' over an ssh connection. For that to work, you need to run 'psconfig ipp-2.6.1' (or whatever the IPP version is called on your system) in your startup file. 102 {{{ 88 103 * Try "ssh myhost pclient". If it works, you can exit pclient with "exit" or "quit". 89 104 * If it doesn't work, you need to check your shell configuration (.cshrc or .bashrc) to ensure the IPP environment is being loaded via psconfig. In .cshrc, just make sure that 'psconfig ipp-2.6.1' is executed. In .bashrc, there's a catch: bash doesn't let you use an alias in the same file that defines it, so you need to expand the 'source' by hand in .bashrc, thus (this fix will be included in the INSTALL instructions in releases post 2.6.1.): … … 94 109 alias psconfig='echo psconfig not available' 95 110 fi 96 * If there is a long delay between executing the "ssh" command and the shell appearing, there may be a timeout problem. 111 }}} * If there is a long delay between executing the "ssh" command and the shell appearing, there may be a timeout problem. 112 {{{ 97 113 * Make sure your shell configuration is not too complex. 98 114 * One bash user had the IPP environment being set up in both .bashrc and .cshrc, so that psconfig was being called first when bash started, and then again on starting psconfig (which is a csh script). This produced a long delay, causing the command to time out in pantasks. 99 * Finally, this can also be triggered by the readline bug, whose fix is described below under [wiki:#detrend_resid_imfile.pl_triggers_the_error_message_'Unknown_option:_--erbose' detrend_resid_imfile.pl triggers the error message 'Unknown option: --erbose']115 }}} * Finally, this can also be triggered by the readline bug, whose fix is described below under [wiki:#detrend_resid_imfile.pl_triggers_the_error_message_'Unknown_option:_--erbose' detrend_resid_imfile.pl triggers the error message 'Unknown option: --erbose'] 100 116 101 117 ==== On startup I get "can't find config file. some functions will be unavailable." Which config file is missing? ==== … … 105 121 ==== How do I re-run files that have failed at some stage after fixing the bug that caused the failure? ==== 106 122 107 Most of the <code>ippTools</code> binaries (which provide the database interaction) have some version of a <code>-revert</code> command. For example, if a camera stage failed, try <code>camtool -revertprocessedexp -cam_id 12345</code>. You can also revert based on an error code using the <code>-code</code>argument.123 Most of the `ippTools` binaries (which provide the database interaction) have some version of a `-revert` command. For example, if a camera stage failed, try `camtool -revertprocessedexp -cam_id 12345`. You can also revert based on an error code using the `-code` argument. 108 124 109 125 ==== Process X succeeded without fault, but it is not moving on to process Y. How do I force it to proceed? ==== … … 113 129 If the process really just stopped without raising a fault and without initiating the next stage, then you can try manually setting its state to 'full' and using the appropriate ippTool to initiate the next process in the sequence. For a stalled chipRun with chip_id 2591, this would be done like this: 114 130 115 <pre> 131 {{{ 116 132 chiptool -dbname myDatabase -updaterun -label 'myLabel' -chip_id 2591 -state full 117 133 118 134 camtool -dbname myDatabase -definebyquery -chip_id 2591 -set_label 'mylabel' 119 </pre> 135 }}} 120 136 121 137 … … 124 140 The dropped character in a long line is a classic symptom of a bad 'readline' library. 125 141 To fix it, do: 126 <pre> 142 {{{ 127 143 % pschecklibs -build -force libreadline 128 </pre> 144 }}} 129 145 There should be no need to rebuild the IPP (since we're using dynamic libraries) 130 146
