| | 23 | sometimes pstamp updates identify chips or skycells that were not cleaned up properly or are in an odd state, but are not needed by the pstamp request -- just updating the full exposure of chips and/or warp skycells will help clear those |
| | 24 | |
| | 25 | the ps_ud_WEB is a good label to use in general since it is always loaded but you can have it be your own if you want to keep a set grouped under that, just be sure to add it to the pantasks (ippitc stdscience for example) so that the updates will be run (and remember if your own label it could get removed by the pantasks auto-restart ~1530 HST) |
| | 26 | 1. '''full chip update from cleanup''' |
| | 27 | {{{ |
| | 28 | chiptool -dbname gpc1 -setimfiletoupdate -set_label ps_ud_WEB -chip_id 1386008 |
| | 29 | chiptool -dbname gpc1 -setimfiletoupdate -set_label ps_ud_WEB -chip_id 1531440 |
| | 30 | }}} |
| | 31 | |
| | 32 | 2. '''full warp update from cleanup requires the chip to be updated too''' |
| | 33 | {{{ |
| | 34 | chiptool -dbname gpc1 -setimfiletoupdate -set_label ps_ud_WEB -chip_id 1240612 |
| | 35 | warptool -dbname gpc1 -setskyfiletoupdate -set_label ps_ud_WEB -warp_id 1188900 |
| | 36 | }}} |
| | 37 | |
| | 38 | * CCL: it is ~30 exp/hr slower than a few days ago ~45 exp/hr. check the ssh tunnel (who?) or try to use the compressed download option (how?) |
