dsavransky
commented
8 years ago Recovering rm journals for issue:
mperrin: Upon more thought I don't think this is a particularly necessary feature. I'm marking it as lowest priority for now but maybe we should just drop it entirely.
mperrin: Figuring out exposure times that won't saturate is actually a common enough task (and an annoying enough one) that we should try to automate it. Here is a first attempt at that. I'd actually put in a while ago some code for displaying an image histogram so there was not a lot needed to add here. You access this from gpitv's Image Info menu then selecting 'Histogram/Exposure'. See attached screen shot.
Right now this is hard coded to indicate an estimated exposure time for which the 99.5% brightness value in the image would reach full well. It's up to the user to be smart enough to dial back from that to half of full well or whatever the actual desired exposure is. We can improve this and add more functionality if in practice that would be helpful.
Code commit 2002.
ingraham: I'm not sure this feature is every really used. I think we can close this out unless someone thinks otherwise. We no longer tweak exposures by a few seconds really...
mperrin: Agreed, this can be dropped.
When looking at a 2D image, there should be a dialog box you can pop up that does statistics on the image, plots a histogram, and recommends what a good exposure time should be to have well-exposed images. (The goal is to prevent people from wasting time at 3 am looking at images by hand trying to decide whether to up the integration time by 5 or 10 seconds or not...)
This tool should be aware of the way that dynamic range decreases for very short exposure times.