Add 'verbose' mode to PSFPhotometry classes
See original GitHub issueI’m doing PSF photometry on some crowded frames and I’ve been staring at a screen that shows no changes for well over 10 min now.
Could a verbose
mode be added to these classes that would print some relevant information regarding the process as it moves forward?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
PSF Photometry (photutils.psf)
This class implements a PSF photometry algorithm that can find sources in an image, group overlapping sources into a single model, fit the...
Read more >profoundFitMagPSF: Fit PSF Magnitudes to an Image in ProFound ...
Fits PSF mags to an image with known source positions. ... In ProFound: Photometry Tools ... Logical; should verbose output be displayed to...
Read more >photutils Documentation - Read the Docs
photutils.psf. – Added BasicPSFPhotometry, IterativelySubtractedPSFPhotometry, and DAOPhotPSFPhotometry classes to perform PSF photometry in ...
Read more >Cross-Filter PSF Matching — STScI JDAT Notebooks
... consistently for every image class Photutils_Catalog: def __init__(self, ... view / save output, but photometry in other filters will be added soon!...
Read more >ProFound: Photometry Tools
'groupstats' output of photometric properties of the groups. ... profound=profoundProFound(image, magzero=30, verbose=TRUE, plot=TRUE).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If this gets implemented, please use the astropy logger (i.e.
log.info()
) and notprint()
calls.I agree that this is a sensible idea.On Nov 15, 2017 8:55 AM, Gabriel Perren notifications@github.com wrote:I was actually thinking of printing relevant information about the state of the process, rather than a progressbar. Of course, this is more complicated since those messages need to be written first. In any case, anything beats staring at a blank screen for an hour.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.