-
Notifications
You must be signed in to change notification settings - Fork 0
ASB-29533: Adding option to save filename checker output in alternate format (csv, fits, excel, html) #32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,10 +8,13 @@ authors = [ | |
| { name = "Mikulski Archive for Space Telescopes", email = "mast_contrib@stsci.edu" }, | ||
| ] | ||
| dependencies = [ | ||
| "astropy >= 7.2.0", | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. astropy and pandas are big dependencies. Since, as far as I can tell, they are needed only for the specific write methods, is it worth making them optional dependencies? or will that cause too much of a headache for users? (I don't have a strong opinion here, just posing the idea)
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Astropy will definitely be strong requirement for the metadata checker, so I'm leaning towards leaving this here. We can revisit later if others feel strongly about it! |
||
| "click >= 8.1.0", | ||
| "openpyxl >= 3.1.5", | ||
| "pandas >= 2.3.3", | ||
| "pyyaml > 6.0.1", | ||
| "setuptools-scm >= 8.3.1", | ||
| "tqdm >= 4.67.1", | ||
| "setuptools-scm >= 8.3.1" | ||
| ] | ||
| dynamic = ["version"] | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not fully sure how useful
fitsformat would be for this file. It is okay to have it an option, and yet I am curious to know how I could effectively use it for inspection.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fits file has two Table extensions, which contains the all the same information from the filename checker output. You can open it however you want, with Python, or with a VSCode extension, or TOPCAT, etc.
For example, in Python you can see which files failed inspection with something like this:
I agree it's not the most practical format for this, but I thought that it would be a good option to include for astronomers more comfortable with fits files than any other format. I hope that helps!