User Interface issues during scheduling

[jchate6]

In Master

• [x] always assume schedule for next available UT date
• [x] No response or error with failed login
• [x] Cadence page displays all proposals instead of user specific proposals
• [x] Link to object Body page from confirmation page
• [x] Link to object Body page from initial scheduling page
• [x] Improved error messages when scheduling fails "Additional information:Parsing error" is not useful for most users.

In Branch issue-207

• [x] link blocks on body to appropriate superBlock page
• [x] display current UT time on scheduler page
• [x] Display site and telescope class on confirmation page (potentially as important than the MPC code)
• [x] Give warning flag if target is bad for requested site.
• [x] Give visibility of target
• [x] ability to adjust exposure time from confirmation page
• [x] display current moon distance
• [x] display current moon phase
• [x] Add ability to adjust the minimum moon distance
• [x] Add ability to adjust the IPP value
• [x] Add ability to alter the max airmass value
• [x] Loosing the ability to edit slot length when too short
• [x] Make scheduling failure more obvious
• [x] Consider returning to Body page after successful (or unsuccessful) scheduling attempt
• [x] Add generic "Telescope Class" scheduling options. (i.e. ANY 1m where the target is visible)
• [x] always update form before submission
• [x] allow for Group-ID to be editable
• [x] hover text for airmass giving altitude
• [x] fix groupID box size in firefox

Automatically generated UT date is not always the current date. Proposed solution: Have the automatic option simply be "Next possible date." This could be the default for generating ephemerides as well.

When editing the slot length on the observation confirmation page, accidentally changing the slot length to be too small results in the user loosing the ability to edit the slot length again to fix the problem. Their only recourse is to start over with the submission process.

This also resets all of the original parameters to their defaults, which is slightly obnoxious, but I believe significantly more difficult to address than the above.

[jchate6]

It seems like the Cadence observations submission page still gives access to the default proposal even if the User does not have permission to use the default proposal.

[talister]

It seems to be worse than this. When I go to cadence mode, I can see your DD time and Ennomos proposal which I don't think you gave me access to. It looks like it is not filtering the ProposalPermissions to build the list of valid proposals for the form.

[jchate6]

Feature196 addresses login error

[jchate6]

There is no way to tell a priori for sure that the jitter in a cadence schedule is longer than the slot length. If this is NOT the case, the scheduler does not let you edit either value, but instead forces you back to the previous window.

[jchate6]

feature/alternating_filters sets UTC to "next dark time" if dark time of current UT date has already ended. Will still throw error for dates set more than 1 day in the past.

[jchate6]

I know adjusting exposure time will be brutal, but for making neoexchange a more generic utility, this kind of basic functionality will be necessary (especially when dealing with different filters.)

[jchate6]

link to body page added in feature/floyds_snr_overhead_calcs

[jchate6]

Proposal Permissions resolved in feature/floyds_snr_overhead_calcs