svvatters / sofialadin Goto Github PK

Need to provide User documentation for SOFIA extension commands, etc

Need to add some info about the extension and licensing. Also need to add CDS Aladin acknowledgement info to git (README?)

When I set the rotation using the SOFIA ROF... menu item the compass updates immediately but the image and overlay layers update at different later. If the user double clicks on a plane right after sending the command the imager and overlays update sooner but not immediately.

The method making the changed needs to call a different refresh method or something to get everything to update immediatley.

They're clunky and it isn't obvious how they should be used. They also don't give feedback about bad input, etc...

LOW PRIORITY SINCE THINGS ARE WORKING AS IS:
All of the supporting .js, .css, & .html files are just in src/ but it would be cleaner to have them under packages like src/sofia/html. When I had them in packages it would run with the -mopsreport flag from within Eclipse but not the standalone .jar file created by build.xml. If I edited getResourceAsStream and the ResourceFile enum in SciObsTrackReport.java so it would run from the standalone .jar file it would no longer run within Eclipse.
Would like to figure out how to include these files in the .jar file under packages.

Add the Track Star Reporter. Want to be able to run it a few ways:

• In its own thread via the Aladin GUI
• As a SOFIA_Aladin command line flag
• As a released standalone jar

Should the command line and standalone versions have any GUI components?

Currently the Reporter only creates reports for "unique pointings" in an input group of Obs Plan xml files. Need to display some reference to the dupes under the unique pointing.

Give the user a final report in the console and make them quit the program when they're ready.

Now the corner stars' table rows are grey text.

Still need to include corner stats in summary table (also on the batch report) and something to tell the user what the grey means.

Sort out how Aladin caches jpg images (dss color) so we can make sure they will be available in-flight.

Right now if we zoom in and out enough Aladin will download jpgs of different resolutions and if we save that .aj file the images will usually be viewable later even when offline. This has failed to work a few times and we were stuck with a white background.

Maybe find out how much space the DSS colored jpg set would take to store locally?

Mixed column layers don't make it into pos file and crash Aladin

The console prints bad lines like "..........blah blah blah" and when it's running the scroll bar fights the user.

addPosOffset help doesn't mention the units of the offset. They are arcseconds.

sometimes it is checked when the FOV isn't displayed and vice versa

Edit Aladin's script help so the built-in Aladin commands include the added coordinate formats it can take as inputs due to the SOFIA-extension

Set up javadoc (with ant) and insert javadoc comments into source files

Make a schema for the ObsPlan files that come from the dcs

If we wanted to add/modify any Obs Plan files to a group of them we'd have to rerun the whole Reporter (could be an hour or more). Need an html page that does the reporting work using JS (dart?) so we could add/modify an Track Star Report and a refresh will update the Batch Report to reflect that.

The JS (dart?) would also need to do the unique pointing thing.

Get the github wiki started and add documentation

CDS page
How to use
Code changes etc

Create a schema for the Obs Plan xml files and then share with Obs Plan users/creators.

Use schema to verify input to ObsPlanReporter.

FUTURE? Do the same for other SOFIA xml formats?

So far all the AladinException and IOExceptions are thrown but need to handle them somewhere

Some of the generated Aladin files produce weird overlay bugginess when viewed in Aladin.

Track reporter can't handle scientific notation.

The batch reporter creates Aladin planes (folders) named "WFI", "FFI", and "FPI". Users may want to make new planes with the same names but they get forced to "WFI~1", etc.

The current state of the criteria table doesn't mention that the UCAC catalog isn't searched out to the WFI-donut (does go out to WFI-corner)

Get TO/MD feedback about how we should define a unique pointing (combination of coords, name, obs id, instrument, configuration, etc...?)

This is part of preparing for the ability to include chops etc. to the reports.

Modify Dillman's TARF Calculator to encapsulate all the pertinent SI variables and run in a gui.

In the future may also be used to set ROF and display SI info on the overlay