2022-05-29: APP 2.0.0-beta2 has been released !
Download links per platform:
Integration looks as if Darks, Dark/Flats, and Flats are not being removed.
I've generally had good results with this fine Post Processor until recently when I moved to a OSC CMOS camera. I've exposed the sensor for 600s lights which may be far too long for this sensor. However, I thought the 600s Darks would eliminate the Amp Glow in the Integrated result. The Sony sensor is apparently prone to three (3) areas of Amp Glow, which is evident. The Integration also shows the vignetting in my light train as well as some other items that should be pulled out with the Flats. I've included matching Darks, and Flats as well as Dark/Flats in the process, but perhaps I'm ticking or not ticking something in the setup that is improper. I'm using APP Version 1.077 presently. I am grateful for any assistance in understanding how to correct my methodology.
Here is mt Master Dark 600s.
I would advice to update APP first to at least 1.079 (1.080 is around the corner), when you load in a light and your masterdark, what happens when you select "L-calibrated" on top of the screen? Do you see the dark being used (it's indicated then in the list on the bottom) and does it correct anything?
First, thank you for your response. It's greatly appreciated. I have updated the revision of the application to the latest v.1.079. Next, I loaded a single 600s light (shot with L-eNhance filter on my OSC camera) in Linear, the loaded the Master Dark (600s) in Linear. Then with the image area of the upper-right corner enlarged to see any changes the MD would have. When I selected "L-Calibrated" I do see some of the "Sensor Glow" streaks disappear but clearly not most of it. Would this indicate that I have a light-leak during either taking the Darks and/or the Lights?
Mm, I do see that your masterdark has a different ISO/gain then your lights. What happens if you tick the "scale masterdark" in tab 2? And I assume the adaptive pedestal/amp glow is also ticked?
And could you also take a screenshot of the masterdark itself? If I can't figure it out, I'll ask you for the masterdark and some lights, just to be able to check it myself. It does seem to work, maybe a bit too much even as the light streaks are now darker. What happens if you now integrate with this, the same result?
Vincent, I did another run, this time with the "scale masterdark" ticked and yes, the adaptive pedestal/amp glow is also ticked. Same result. The appearance of Dark & Flat artifacts. I'll attach my Master Dark ffile here.
Thank you for your efforts in helping me. It is great having someone to turn to for advice.
This is my Master Dark
Doesn't seem to be very weird at first glance, apart from the big amp-glow signal. Could you upload the masterdark and like 10 light frames?
You can upload them to our server (<- click that link) with username/password: appuser
Please create a directory called "dalemschultz-ampglowproblem" and I'll have a look asap.
Thinking that perhaps 600s subs were too long for the Sony Sensor, last night I took 26 subs at 300s and re-shot my 300s Darks as well. This time the Darks were at the same ISO! I only used 10 of the subs (total, 50 minutes) and I can't see where I did anything different in the tabs 0-6, but the results are good for me. Here are the 300s Master Dark and the same Flats as before (I'm reshooting the Flats tonight), along with the satisfactory Integrated image before any additional processing.
Masterdark (300s, ISO 120)
It might also be that the ISO difference was the issue, perhaps in this case (with that amp glow) that doesn't work too well. Anyway, great to see it worked!
I've tried several times to log in to the Server to upload those lights and Masterdark, but I haven't been able to. I'm using my APP login, Username, and Password, but no access. I'd still like to understand why the Integration result of a batch of 600s lights and 600s Darks (matching iso) along with Flats, is showing most if not all of the noise from the Masterdark and the Masterflat. Honestly, I'm a bit unclear about the usage of the right-hand side variables.
These are the defaults when I start APP. Is there a resource where I can review their usage. I've looked for the manual, but use the hover tools that are present.
Master Dark, 600s, iso 121.
Master Flat, 0.08s, iso 120.
It's hot here now and I'm only able to get my ZWO sensor down to about -14, so perhaps shooting 600s subs is too long and produces too much noise. Maybe I should reserve the longer subs for the cooler months? Thinking out loud...
If you can help me understand the login for the Server, I'll be happy to upload those files.
Many thanks Vincent,
This is an outline of my procedure for taking Flats.
1. At night, I'll use an iPad placed on my objective with a blank screen showing, illuminating the sensor.
2. Use the SGP "Flats Calibration Tool" that saves the required exposure times & iso into the "Filters" area of my equipment profile in SGP.
3. Use the "Flats Wizard" in SGP to take the Flats images that targets an exposure +- 500 ADU's from the 30,000 ADU's for that sensor.
4. Take the night's run of Lights.
5. Load those Lights & Flats into APP, then create a Master Flat, during Post.
I think that's it.
I too have just had a scenario where my calibration frames are being ignored too. APP 1.080
Processing my tri-band data from my OSC.
0) Ha-Oiii Extract Ha and it appeared to be ok. See Integration result below:
I then went back to change this to
0) Ha-Oiii Extract Oiii, accepting the fact the data needs to be re-normalized. I didn't change anything else. The result is this mess:
I never had this issue with the Beta release of 1.080 as I processed similar data in the same way last week with no issues.
I decided to process 0) Ha-Oiii Color and ended up with this:
I'll retry with an older version of APP as well as verify if calibration is happening. My workflow is very simple and I don't have any unusual or incorrect Gain settings etc. My Flats, DarkFlats, Lights and Darks all at same Gain (and offset where applicable).
Correction - I see the same problem in 1.080-Beta2:
I'm now not sure how I managed to process last week's data as I didn't have these issues. Why is this occurring? Why is it my HaOiii Extracted Ha process is giving good calibrated data, but HaOiii Extracted Oiii isn't?
And I hijacked this thread because of the relation to the inability to apply calibrated data, but let me know if this is a separate issue.
** UPDATE: I'm still getting this with 1.079 too so something is wrong - but I really can't work out what. My Ha-Oiii Extract Ha is calbrating fine. My Ha-Oiii Extract Oiii is not being calibrated correctly **
Update: The problem in my specific case [and I apologise for distracting in this thread] but it was my Flats that were the problem. The part of the workflow that had changed since last time I processed data was NINA [capture software]. I had updated this since last week. It changed some things in the Flat Wizard and I didn't verify the Flats/DarkFlats it produced. They were far too bright. Processing correct ones and my calibration issues have gone away.
Apologies for the delays, @dalemschultz. To me it looks like the flats are not correct, a nice flat should not have a rectangular spot in the frame (is that the iPad?). You should have the same focus and the sensor should be illuminated fully and I think this might be one of the issues here. I also see that the dark is not corrected, so this makes me think that the calibration frames are either not taken with the proper camera settings or have different dimensions which makes APP not be able to either correct properly or even match them. You can load a light into APP, then you Masterdark and Masterflat and on top of your screen, select “l-calibrated”, in the list APP should then add indications to the light frame that they have been added and the correction is loaded. If they are not added, the data is somehow wrong.
@itarchitectkev Thanks for finding this out on your own! Great to know these things as I can use things like this to find other people’s issues faster too. 🙂
Thank you or your patience on this. I wondered about the pinkish rectangle on the Flats as well. Either way, I'll reshoot them with a different light source tonight. Then try a new run in APP to check the results.
No worries, if it doesn’t work still, we can look further into it together. That’s how we learn anyway. 🙂
I've been busy scratching my head about the pinkish rectangle on the Flats images and I've discovered the source of it. I'm shooting at full focal length (952mm) with my Refractor and I'm using the Optolong L-eNhance dual-band filter. It has a pink look to the coatings that provide the bandwidth rejection. The iPad was not the issue since I was pretty sure I had seen the pink rectangle previous to and subsequent to using it. Today I used the overcast sky to capture T-shirt Flats and the pink rectangle is present when using the L-eNhance Filter, but not when I use my Infrared Filter, which is mostly clear. SO, that issue is known, but the issue of using the Refractor without the benefit of a Reducer/Corrector shows itself as pretty bad vignetting and probably Coma. I've included images of the Flat files directly from SGP as well as the files after they are loaded in APP, including both the L-eNhance & IR filters. Today, I decided to clean all accessible optical surfaces. I found a tiny spider suspended in its tiny web all the way up the inside of the 127mm Refractor! Fun! That means I needed new Flats as well as any Lights, which I'll attempt tonight, clouds permitting!
SGP's view of Flats, LeNh (0.16s, iso 120) & IR (0.03s, iso120). Note, no pink rectangle on the far left one L-Enhance Filter.
APP's view of Flats, IR (0.03s, iso 120 & LeNh (0.16s, iso 120). Note the pink rectangle on the right one with the L-eNhance Filter.
Taking Lights tonight, hopefully!
Thanks so much Vincent!
Well, that’s a lot more knowledge at least! 😉 I also see that you could increase the exposure on your flats, the histogram should be a bit more to the middle. I’m still a bit puzzled by the rectangle, but it must be some optical effect then.