fritz-marshal / fritz-beta-feedback Goto Github PK
View Code? Open in Web Editor NEWA place for beta testers to discuss issues or request new features related to the Fritz Marshal
A place for beta testers to discuss issues or request new features related to the Fritz Marshal
Is there currently any discussion about the possibility of expanding the current classification taxonomy list, if can we add a method for the user to create a new classification type? For example, there are many kinds of (sub-types of Type Ia supernovae) and other kinds that are currently not on the classification/taxonomy list.
When displaying the spectra for ZTF20acpiywu the listed vs. plotted spectra are mismatched.
To Reproduce
Steps to reproduce the behavior:
Platform information:
It would be good to have all the group names displayed somewhere and an easy way to join them. For example, it could be there a button to send a request to join directly to the admins of the group. If this is too complicated, we should be able at least to see the name and email of the PI/admin that we have to contact.
Hi -- I just saved the source https://private.caltech.edu/source/ZTF20aceyolc, but compared with its photometry on the old Marshal (http://skipper.caltech.edu:8080/cgi-bin/growth/plot_lc.cgi?name=ZTF20aceyolc), there are less data points on the Fritz page. May I know what is the reason for this?
Thanks,
Yuhan
Current objects coordinates on Fritz are "02h54m59.2s +04d03m36.87s", which don't parse well to other tools. Request to be updated to the format "17:25:39.16 +59:26:48.4" as on Growth Marshall. Also would be good to have in degrees too as on GM.
Would it be possible to add a button for each source to download the uploaded spectra directly from Fritz instead of using the API?
Suppose we wanted to upload a spectrum from a telescope that is currently not on the current instrument list (in the upload spectrum section of each source). Are there any existing methods (API and manually) to add new telescopes to the instrument list?
Somewhere on the dashboard, ideally, right next to the observatory forecast/webcam, it would be nice to add a tab for the following:
Hi,
The lines of the spectra appear to be non-solid. Could you show them as solid lines?
It would be important/critical to have the following features like on the old Marshal:
-rebin spectra
-overlay telluric lines
-overlay typical galaxy lines (absorption and emission)
-add lines from WN/WC/WO stars; critical for infant SN studies
-define the velocity of each spectral feature; SN features will not have the same velocity
-blank fields to add customised lines
-display which lines are shown when you hover over the element
-add comments to individual spectra. should also be shown next to the spectrum
Cheers,
Steve
Feature Summary
If a candidate/source is nearby another candidate/source (<5" or whatever the criteria was on Growth marshal), mention this information on source page/candidate page
Usage / behavior
Need to know if two sources are duplicates of each other but have different ZTF IDs, helpful in case of nearby Novae
Implementation details
A comment (either just below ZTF name or in annotations) that a source is within x" from another (if x<5)
Hi,
The current default option is to save an object to all filters it passes. This is a rare use case. Scanners will save transients to specific programs and not all filters.
At the moment it takes 3 clicks to save a transient to a specific program. This can be reduced to two. If only one program is selected, this program should be the default to which an alert is saved. In case multiple filters are selected, the default program should be the one at the top of the alphabetic ranking.
Having a faster save option is particularly important for SLSN and RCF filters that save many targets every night.
Cheers,
Steve
Please fill out relevant sections below; remove those that are unused.
Describe the bug
At least three users cannot display the observing run https://fritz.science/run/2
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Open the observing run page
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information:
Additional context
We are observing tomorrow, so it would be great to have this solved asap. Thanks.
Please fill out relevant sections below; remove those that are unused.
Describe the bug
For some sources, the offset stars in the starlist and those in the finder chart are different
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The offset stars and offsets in the finder and the starlist should be exactly the same!
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information:
Additional context
Please fill out relevant sections below; remove those that are unused.
Describe the bug
The targetlist for P200 generated by Fritz is not accepted by the P200 system. There are several formatting issues.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The expected format of the P200 targetlist is as follows -
20 characters for target name (if name<20 chars, remaining chars are blank)
2 characters for RA hours, 1 space 2 characters for RA minutes, 1 space, 2 characters for RA seconds
2 spaces
2 characters for Dec deg, 1 space, 2 characters for Dec minutes, 1 space, 2 characters for Dec seconds
1 space
2000.0, 2 spaces, !, comments
Example :
ZTF20acppuiq 00 09 01.32 -08 35 54.76 2000.0 ! source_name=ZTF20acppuiq
Platform information:
Additional context
It will also be helpful if the following standard stars are added to the list
G191-B2B 05 05 30.60 +52 49 56.0 2000.0 ! Standard
Feige34 10 39 36.71 +43 06 10.1 2000.0 ! Standard
Feige67 12 41 51.83 +17 31 20.5 2000.0 ! Standard
Feige110 23 19 58.39 -05 09 55.8 2000.0 ! Standard
BD+28d4211 21 51 11.07 +28 51 51.8 2000.0 ! Standard
BD332642 15 51 59.89 +32 56 54.3 2000.0 ! Standard
Describe the bug
It appears that if you go on the Observing Runs page and click on an observing run (for example DBSP 2020-11-18), and try to mark it as "observed" or "not observed" on the actions. The problem is that if the user has not assigned the source, they cannot mark the source as observed/not observed (it returns a permission issue..).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Either if you're part of a specific science group, you should have the ability to mark it done or not done. Alternatively, all users should have the ability to mark as observed/not observed
Other information:
Please fill out relevant sections below; remove those that are unused.
I want to flag an object as observed. However, Fritz complains that I do not have permission to do so.
Expected behaviour
Everybody should be able to change the status of an observation. We need to focus on science, not bureaucracy!
Hi, I saved the source to fritz https://fritz.science/source/ZTF20achvlbs
but there is no plotted photometry. May I know why? Thanks! --Yuhan
Hi all,
I just have a few minor recommendations for the manual upload spectroscopy and the spectrum toolbar.
Can the observers & reducers list be sorted alphabetically? This can be quite hard to find one user when some filters have many users associated
Observation MJD, can this be converted to MM/DD/YR format?
Spectrum lines tabs, redshift, and V_expansion are currently not working
Can we include a binning factor to the spectra displayed on the source page? This can be particularly useful to increase/decrease the spectrum resolution
Thanks! 🔭
I would be useful with a sandbox group/filter where api connections can be developed and tested without either having to create new groups all the time or polluting/interfering with existing ones. A sandbox can be emptied regularly (daily) except for some sample interaction objects.
I want to have permission to remove sedm trigger for https://fritz.science/source/ZTF20acpjapi
New
danny 7:13 AM
Currently we dont let people delete other peoples’ requests
jesper 7:22 AM
How do we change this?
stefanv 7:24 AM
You can file a feature request at https://github.com/fritz-marshal/fritz-beta-feedback
fritz-marshal/fritz-beta-feedback
A place for beta testers to discuss issues or request new features related to the Fritz Marshal
Last updated
a month ago
https://github.com/fritz-marshal/fritz-beta-feedback|fritz-marshal/fritz-beta-feedbackfritz-marshal/fritz-beta-feedback | Oct 13th | Added by GitHub
On the GM we had this feature on the home paged called Spectra Summary. Essentially, the user was able to query for a given date all the spectra that have been uploaded in that date range to GM and filter it by classification, instrument, and science program. It would be awesome if we can add this feature somewhere in Fritz, and it would help a lot in managing our classification and spectra.
Hi,
The number of photometry of ZTF20abzumlr is different on https://fritz.science/alerts/ztf/ZTF20abzumlr and https://fritz.science/source/ZTF20abzumlr.
Hi,
The option to query HEASARC has no underlying link.
Cheers,
Steve
Very small detail but the webcam to the Palomar telescopes should point to
http://algol.palomar.caltech.edu/instruments/allsky/AllSkyCurrentImage.JPG for night time sky conditions. And fwiw there also the inside the dome cam and the view from High Point which looks down on the all the Palomar telescopes
http://nera.palomar.caltech.edu/upload/p48/p48-webcam-latest_1.jpg
When uploading swift photometry from UVOT the filters are not recognized and are not supported in the documentation here: https://skyportal.io/docs/api.html#/paths/~1api~1photometry/put, specifically there is no filter field for UVW2, UVM2 and UVW1 UVOT filters.
I understand this was supported before on fritz so i submit this as a bug.
Hi,
The photometry and spectroscopy should have dedicated pages and not only show up on the object dashboard. We need to see the photometry as a table without downloading the light curve.
Which features are supposed to go into the spectroscopy tool? Do you plan display lines like on the old Marshal? If yes, which lines are you going to add to the catalogue?
Cheers,
Steve
Hi,
And a few comments on the group page.
Critical
-User names should be real names, not acronyms or pseudonyms
-Name list has to be alphabetically sorted
-We need an option to add a batch of users at ones.
Cheers,
Steve
Can each user have a list of "Favorite Sources" somewhere on the dashboard? Similar to the GM, each source had the option to be saved to a list of favorite candidates. Would it be possible to add something like this to Fritz?
It appears that the centroid plot for each source is not entirely accurate. For most sources, the offset estimates are always ~0 when in fact if you look at the science images there's clearly a pretty obvious offset from the host nucleus.
Right now, it looks like the centroid is being calculated from the alerts alone, ideally, this would need to be done with respect to the host coordinate.When adding users to a new group or selecting additional admins for a group, the current dropdown of users seems randomly ordered. It would be much easier if this was sorted alphabetically.
Hi,
Thanks for the improved scanning page! I agree with Jesper that several of the previous comments still apply. This would be my list.
High priority
-Time axis has to be in units of time from now. MJD is useless if you want to judge whether a transient is 2 or 20 days old.
-Reject options like on the old Marshal
-Menu “Show previously saved candidates?” like on the old Marshal
-If a classification available, show it (don't know whether this feature already exists).
-Examine option of the cut-outs. Critical for fast and young transient experiments.
-ZTF image cutouts have a too-small dynamic range.
Low priority
-Colours of the ZTF filter changes depending on the number of filters. The colour of the filters should be fixed: g = green, r = red, i = yellow
-Annotations should be collapsed by default. This makes it easier to judge which filters a given alert passed.
-Offer an option to export candidate list to a text file
-Reduce white space between postage stamps.
Cheers,
Steve
Would it be possible to remove old observing runs under the Assign Target to Observing Run tab under each source? Currently, it looks like there's still an option to add sources to observing runs from October, which might lead to confusion/accidents assigning candidates to old runs (see image below).
I purpose that we can leave all the past observing runs in the Observing Run section, but ideally, I think it would be more user-friendly oriented if on the source page, you can only see the upcoming runs. Thanks :)
Hi,
Could you alphabetise the telescope list on the dashboard?
The Gemini telescopes are written as GS and Gemini North. It would be more useful to have a consistent naming scheme. :)
How can I watch the status of multiple telescope sites?
Cheers,
Steve
Hi,
and comments on the object page.
High priority
-Examine option of the cut-outs
-Improve the dynamic range of the ZTF cut-outs
-Observability option
-Absolute magnitude on the right y-axis of the light curve plot. Not shown even when redshift exists.
-Spectra are not displayed (Dima and Danny have pointed me to the thread where the spectral module is discussed.)
-Auto-annotations have to include when and by whom an alert was saved and/or removed from a specific program (date and hour are needed; critical for fast and young transient experiments). Even when manually adding a source. The "Source save history" is not a good solution. We sometimes need to inspect this quickly.
-Besides the object page dashboard, dedicated photometry and spectroscopy pages (to view/access the full data and properties)
-Photometry table without the need to export the light curve
-Option to inspect the full alert packages.
-Option to only show positive subtractions. Vital for all SN experiments (previously discussed on Slack).
-Option to force-check whether all ZTF Photometry is shown in the light curve.
-Option to ingest photometry from PS1 DR2 and (i)PTF
Medium priority
-If the window size is changed, the comment section behaves differently from the rest.
-Cut-outs should have at most 3 elements per row. Doesn't work always (see attached picture).
Low priority
-Fontsize in the survey sections doesn't seem to be the same for all elements.
-CRTS and FIRST buttons have a different structure. You can't right-click them to open in new tab.
-IRSA/PTF search is not performed.
-IRSA/WISE search fails.
Cheers,
Steve
Would it be possible to use Fritz to show the photometry as a function of time for all known asteroidal sources taken from the alert stream? Showing the photometry as a function of time would enable monitoring of asteroid brightness and detection of sudden brightening events such as those cause by disruptions.
The Fritz Marshal User Guide mentions external catalogs that can be crossmatched against but the list of what is available is not mentioned anywhere.
Hi,
The following buttons also don't work:
There is a problem with the Java for
PyMP and LCOGT are incorrectly linked.
IPAC is spinning and spinning but shows no result.
Cheers,
Steve
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.