Context Navigation

Changes between Version 38 and Version 39 of PS1_IPP_Czarlog_20121203

v38	v39
85	85	* 13:30 MEH: stack gets 2x wave4 back in, adding ipp060 which is normally out. MD05.refstack can run with stdscience on compute3 so have started there unless LAP stacks start lagging warps.
86	86	* 13:50 MEH: ipp020 has given up on some mounts, rebooting and turning off lm_sensors on startup.
87		* 14:25 MEH: ipp010 neb-host up, will do others in sequence to see if rpc.statd restart and lm_sensors off have cleared.
	87	* 14:25 MEH: ipp010 neb-host up, will do others in sequence to see if rpc.statd restart and lm_sensors off have cleared. stdscience also has 7x wave1, seems possibly excessive. turning one of those off for - ~8 nodes.
88	88	* 14:55 ipp011 neb-host up (neb-host has date stamp now for tracking)
89	89	* 15:00 Bill: Two staticsky runs have y band inputs that generate unreasonable numbers of detections (> 200,000). Since they are y band these cause forced photometry detections for the other bands. This causes memory explosion when processing. If the runs had completed, they would generate ~2,000,000 false detections for dvo and psps and ultimately the user. I have updated the stack tables to mark the offending stacks as bad quality and removed them from the corresponding staticskyInput. The stack_ids are 1094024 and 1494695.