Skip to content
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

Suggestions #8

Open
igorandreoni opened this issue Dec 31, 2020 · 1 comment
Open

Suggestions #8

igorandreoni opened this issue Dec 31, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@igorandreoni
Copy link

The application is neat, congrats on the great job!

Here are a few suggestions, which you may take into account or disregard as you please. Some are surely subjective.

--
In the dynamic output plot, would you consider displaying the light curve in both flux and magnitude spaces, maybe using a tab menu? Many optical time-domain astronomers could find it handy to be able to rapidly switch between the two.

--
Again about the dynamic plots. Is there a way that I cannot see to pan, or go back to the original view after zooming in? Have you considered using bokeh to visualize this plot, which has a nice toolbar that could make it even easier to navigate it?

--
The idea of the PDF plot is nice, especially thanks to the dates in multiple formats. On the other hand, the result can be confusing, see for example
https://fallingstar-data.com/forcedphot/queue/3664/pdfplot/
or the magnitude axis in https://fallingstar-data.com/forcedphot/queue/3661/pdfplot/

I would find it more useful to see two separate plots, one for magnitudes and one for flux, with the plot in magnitude space showing upper limits where mag > mag5sig.

--
In the input box and the API request (and therefore in the output), it would be good to have a column (optional?) for the transient name. This can be particularly useful if one submits multiple requests for an object with slightly different coordinates, for instance because they become more precise or because of the source's proper motion.

@lukeshingles lukeshingles added the enhancement New feature or request label Jan 4, 2021
@lukeshingles
Copy link
Owner

lukeshingles commented Jan 18, 2021

The application is neat, congrats on the great job!

Here are a few suggestions, which you may take into account or disregard as you please. Some are surely subjective.

Much appreciated. Sorry I'm slow at getting back to you.

In the dynamic output plot, would you consider displaying the light curve in both flux and magnitude spaces, maybe using a tab menu? Many optical time-domain astronomers could find it handy to be able to rapidly switch between the two.

I will add the flux plot switcher to my to-do list. We originally were plotting in flux space before we switched to magnitudes, so it shouldn't be too difficult for me to re-enable that and make a a toggle widget.

Again about the dynamic plots. Is there a way that I cannot see to pan, or go back to the original view after zooming in? Have you considered using bokeh to visualize this plot, which has a nice toolbar that could make it even easier to navigate it?

Double tap/click on the y-axis tick numbers to reset the plot. Using Bokeh would take a more time to implement but I'll look into that for a future update. For the moment I am reusing Ken Smith's Plotly script from the ATLAS object pages.

The idea of the PDF plot is nice, especially thanks to the dates in multiple formats. On the other hand, the result can be confusing, see for example
https://fallingstar-data.com/forcedphot/queue/3664/pdfplot/
or the magnitude axis in https://fallingstar-data.com/forcedphot/queue/3661/pdfplot/

I would find it more useful to see two separate plots, one for magnitudes and one for flux, with the plot in magnitude space showing upper limits where mag > mag5sig.

PDF plots are being generated by Dave Young's script (https://gist.github.com/thespacedoctor/86777fa5a9567b7939e8d84fd8cf6a76). I can pass on the feedback, but another option is that you write your own custom plot script (that reads the text data files and makes an output plot file). I could consider adding it to the website as an alternative plot type.

In the input box and the API request (and therefore in the output), it would be good to have a column (optional?) for the transient name. This can be particularly useful if one submits multiple requests for an object with slightly different coordinates, for instance because they become more precise or because of the source's proper motion.

This is what the 'Comment' field is for - to identify the requests by something more meaningful than just the coordinates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants