Changes between Version 129 and Version 130 of ppStack_testing_201111

Timestamp:

Jun 27, 2012, 2:49:19 PM (14 years ago)

Author:

Mark Huber

Comment:

--

ppStack_testing_201111

@@ -49 +49 @@
 == Status ==
  * ...
- * ''6/19'' merged trunk () to pptack_test branch again, so tests now will be using
+ * ''6/19'' restarting to look at target PSF, merged trunk (r34040) to pptack_test branch again, so tests (target PSF) now will be using that
  * ''6/20'' added simple PSF model option to use mean FWHM + X for Target PSF for testing
  * ''6/21'' finally brought page up to date with notes.. reset testing directories for target PSF tests and re-ran initial simtest set.
-
+ 
 
 == Other Issues/Problems ==
-Will add to as things are found/discussed
- * hard limit on number of inputs (was shell descriptors limit of 1024 easily being reached with image,mask,weight,psf,cmf files for each input. Raised to 65535 now by default.)
- * selection of target PSF FWHM, worse input PSF not necessarily best choice as could end up being rejected and only a few inputs may be that large (not representative)
- * heavy RAM use (10-20GB typical for 100+ inputs) -- tests run unoptimized, will need to look at effect 
- * long run-time for 20+ inputs, 400 inputs order 12-14hr (use method similar to psphotStack?) -- tests run unoptimized, will need to look at effect
- * seeing more of the fault 5 stack events for MD nightly where inputs have strangely small <2 pixel input PSF. BIll has quality setting but not turned on, more of an issue possibly with the PSF determination for edge skycells with possible poor extrapolation from center of the field. not really a ppStack issue but..
+Will add to as things are found/discussed:
+ * (fixed) hard limit on number of inputs
+  * was shell descriptors limit of 1024 easily being reached with image,mask,weight,psf,cmf files for each input. Raised to 65535 now by default in shells.
+ * (in progress) selection of target PSF FWHM
+  * worse input PSF not necessarily best choice as could end up being rejected and only a few inputs may be that large (not representative)
+ * (on hold) heavy RAM use 
+  * 10-20GB typical for 100+ inputs -- tests run unoptimized, will need to look at effect 
+ * (on hold) long run-time for 20+ inputs
+  * 400 inputs order 12-14hr (use method similar to psphotStack?) -- tests run unoptimized, will need to look at effect
+ * (on hold) stacks (nightly and deeper) seeing more of the fault 5 stack events 
+  * for MD nightly where inputs have strangely small <2 pixel input PSF. 
+  * Bill has code for quality setting but not turned on, more of an issue possibly with the PSF determination for edge skycells with possible poor extrapolation from center of the field. 
+  * Not really a ppStack issue but needs to deal with and not fault.
+ * convolved stacks have different background than unconvolved stacks?
+