Giter VIP home page Giter VIP logo

fritz-beta-feedback's People

Contributors

dmitryduev avatar stefanv avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

fritz-beta-feedback's Issues

[Feature Request] - Expanding the Classification Taxonomy

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.

Galactic extinction doesn't work

Hi,

I tried to get the Galactic extinction of ZTF18acenqto. When I press the button. I get the following output.
Screenshot from 2020-10-20 11-14-00

Cheers,

Steve

Mismatch of plotted spectra

When displaying the spectra for ZTF20acpiywu the listed vs. plotted spectra are mismatched.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://fritz.science/source/ZTF20acpiywu'
  2. Scroll down to 'spectroscopy'
  3. Click e.g the "green" Lick 3-m/KAST (2020-11-15) or "purple" Palomar 1.5m/SEDM (2020-11-16) - these are mislabelled. (The "purple" Palomar 1.5m/SEDM (2020-11-16) shows the Lick 3-m spectrum, and vice-versa. The correct info is however shown when you hover your mouse on top of the spectra.)

Screenshots
Screenshot 2020-11-21 at 13 59 41

Platform information:

  • Fritz version: v0.9.dev0+git20201118.8603e11.
  • Browser: Chrome, Mac OSX

Request admittance to a group

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.

Telescope coordinates are incorrect on Fritz

Some of the telescopes have longitudes in the domain [0, 360], while others have longitudes in the (correct) domain [-180, 180]. This breaks the observability page:

Screen Shot 2020-11-12 at 3.24.07 PM.png

Need to correct these longitudes so they are on the right system.

[Feature Request/Question] - Expanding Instrument List

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?

Feature requests: spectroscopy

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

Screenshot from 2020-10-20 11-58-08

Tag duplicate sources

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)

Additional context
Adding GM screenshot
image

Too many clicks to save an object on the object page

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

Missing epochs in ZTF20acrinvz

Looking at the lightcurves of ZTF20acrinvz in both the Growth Marshal and in Fritz I see an extra observation in g band in the growth marshal that does not show up in the fritz
image
vs
image

observing run keeps loading

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:

  1. Go to 'https://fritz.science/run/2'
  2. Error appears for a few seconds "Object of type MaskedConstant is not JSON serializable"

Expected behavior
Open the observing run page

Screenshots
If applicable, add screenshots to help explain your problem.
Screen Shot 2020-11-18 at 1 10 54 PM

Platform information:

  • Fritz version: v0.9.dev0+git20201117.9e4dd70
  • Browser: Safari
    • [x ] I'm browsing on a desktop
    • I'm browsing on my phone

Additional context
We are observing tomorrow, so it would be great to have this solved asap. Thanks.

Different offset stars in the finder and starlist

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:

  1. Go to 'Observing Runs'
  2. Click on '2020-11-18 DBSP/Palomar 5.1m Hale (PI: Shri Kulkarni / Group: Redshift Completeness Factor)'
  3. Scroll down to 'ZTF20abfcszi'
  4. Click on PDF finder chart. Note coordinates of ZTF20abfcszi_o2 and ZTF20abfcszi_o3
  5. Scroll further down to Starlist. Select Facility as P200. The coordinates of ZTF20abfcszi_o2 and ZTF20abfcszi_o3 in the starlist are different from the ones noted in step 4.
  6. Same error for multiple other sources including ZTF20acqxzdy_o2 and ZTF20acqxzdy_o3, ZTF20achaxsk.

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:

  • Fritz version: v0.9.dev0+git20201117.9e4dd70
  • Browser
    • I'm browsing on a desktop

Additional context

Palomar starlist format not correct

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:

  1. Go to 'Observing runs '
  2. Click on any observing run ex.
  3. Scroll down to 'Starlists and offsets'
  4. Click Facility -> select P200
  5. The targetlist is not in the P200 format

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:

  • Fritz version: v0.9.dev0+git20201117.9e4dd70
  • Browser
    • I'm browsing on a desktop

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

Lightcurve of ZTF18acenqto is incorrect

Hi,

I manually added ZTF18acenqto to Fritz. ZTF18acenqto has ZTF measurements starting from December 2018. These measurements are not shown. Instead, the light curve shows photometry from the past 50 days. The SLSN is too faint to be detected by ZTF.

Cheers,

Steve

Screenshot from 2020-10-20 11-27-33

[Bug Report] - Permission Issue with Marked as Observed/Not Observed

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:

  1. Go to the Observing Runs page
  2. Click on Plan for: 2020-11-18 DBSP/Palomar 5.1m Hale......
  3. Go to any source that you have not assigned, and go to actions and try to mark as "observed" or "not observed"
  4. See error!

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

Screenshots
Screen Shot 2020-11-19 at 12 48 01 PM

Other information:

  • Fritz version: v0.9.dev0+git20201118.8603e11.
  • Browser
    • Google crhome from my Macbook

Permission issue with observing runs

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!

[Request] Upload Spectroscopy & Spectrum Toolbar

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! 🔭

Sandbox feature for filter/api development.

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.

permissions to delete and edit sedm requests

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

[Feature Request] - Spectra Summary Page

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.

No link to HEASARC

Hi,

The option to query HEASARC has no underlying link.

Cheers,

Steve

Features needed for the photometry and spectroscopy tools

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

Sources not appearing in source search-box

It seems like some sources do not appear in the search box if they have been saved from the alerts page. Unclear if this is due to the source being saved without selecting a group or belonging to a group to which I don't have permissions.

Screenshot 2020-11-17 at 10 27 21

Group page

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

Scanning page: What does "Show previously saved objects mean"?

Hi,

What exactly does the option "show previously saved object" mean? After choosing this option, some saved objects are still shown. We need the same functionality as on the old Marshal to specify what we want to see and what not.

Screenshots are attached.

Screenshot 2020-11-12 at 08 24 16

Screenshot 2020-11-12 at 08 27 45

Contrast settings of cut-outs

Hi,

The contrast settings of the ZTF cut-outs need some further tuning in case of very bright sources or for vignetted images (an example is attached).

Screenshot 2020-11-11 at 18 41 21

Possible Bug with Centroid Plot

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.

Screen Shot 2020-11-13 at 1 29 54 PM

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.

User lists should be alphabetical

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.

Scanning page comments

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

[Feature Request] - Remove Old Observing Runs from Assign Target to Observing Run Tab

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).

Screen Shot 2020-11-17 at 9 40 30 AM

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 :)

Object page

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

Screenshot from 2020-10-28 09-53-31

Known asteroid photometry and lightcurve from public alerts

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.

List of external catalogs

The Fritz Marshal User Guide mentions external catalogs that can be crossmatched against but the list of what is available is not mentioned anywhere.

Further survey buttons don't work

Hi,

The following buttons also don't work:

  • FIRST (not linked)
  • CRTS (not linked)
  • Variable Marshal (Search) (not linked)

There is a problem with the Java for

  • SkyView
  • IRSA/WISE

PyMP and LCOGT are incorrectly linked.
IPAC is spinning and spinning but shows no result.

Cheers,

Steve

Object rejection on the scanning page

Hi,

It is critical to have the option to remove objects from the scanning page because they are bogus, not relevant for a specific program, stars etc. A screenshot with the rejection options from the old Marshal is attached.

Screenshot 2020-11-12 at 08 27 52

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.