Changes between Version 11 and Version 12 of PS1_IPP_Czarlog_20190304
- Timestamp:
- Mar 7, 2019, 12:51:47 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PS1_IPP_Czarlog_20190304
v11 v12 329 329 cp ipphosts.mhpcc.config ipphosts.mhpcc.config.190307ori 330 330 cp ipphosts.mhpcc.config ipphosts.mhpcc.config.190307_target128 331 332 add ipp128 to the skycell metadata 333 334 change the file 331 }}} 332 Then add ipp128 to the skycell metadata by changing the file: 333 {{{ 335 334 ipphosts METADATA 336 335 camera STR skycell … … 369 368 sky31 STR ipp128.1 370 369 END 371 372 copy that back into the default one and then also to psconfig 373 370 }}} 371 copy that back into the default one and then also to psconfig: 372 {{{ 373 cp ipphosts.mhpcc.config.190307_target128 ipphosts.mhpcc.config 374 374 cp ipphosts.mhpcc.config.190307_target128 ~/psconfig/ipp-20170121.lin64/share/pantasks/modules/ipphosts.mhpcc.config 375 376 }}} 377 375 }}} 376 and then restart the pantask : 377 {{{ 378 $> pantasks_client 379 pantasks: stop 380 pantasks: shutdown 381 }}} 382 Between the stop and shutdown check that the jobs have finished, if any, by querying the 'status' or 'controller status' 383 384 ssh into ippc30 as ippitc to restart the pantasks_server, doing what we did before: 385 {{{ 386 start_server.sh stdscience 387 }}} 388 Then to load the config and start it running, do the following in pantasks: 389 {{{ 390 pantasks: server input input 391 pantasks: setup 392 pantasks: run 393 }}} 394 That should get ipp128 to be targetted. As always make sure all the used labels are added to the pantasks, and processing should commence. 378 395 === Friday : 2019.03.08 === 379 396
