%TOC% ---+ Conventions * All angles or coordinates are stored internally in *radians* * All angles or coordinates mostly are presented to the user in *degrees* (sexagesimal format for stars) * double must be used as storage ---+ Use cases ---++ Observability of a source (or list of sources) for a given interferometer |Inputs| User format | internal format | |Star coordinate | anything valid (name or any std coords) | RAJ2000,DEJ2000 | |Observing site location | selection of one supported observatory | [[http://jmmc.fr/~upsa/oischema/http___www.jmmc.fr_aspro-oi_0.1/complexType/InterferometerDescription.html][observatory reference]] | |Date of observation ( or period of time )|like DDMMYYYYHHMM| (Modified) Julian Day ( precise up to the second )| Plot outputs: TODO : How to represent the observability of a list of star onto multi-telescope ---+++ Is the source visible in the sky ? ---++++ Is the source over the horizon ? |outputs|Internal/User| Format | | celestial coordinates | Internal | HA / delta ?? units TBC TBD | | over the horizon | User | boolean | ---++++ What is the AirMass value ? |Inputs| User format | internal format | | Seeing | choice or value ? | TBD | | Humidity / Temperature... | choice or value ? | TBD | |outputs|Internal/User| Format | | AirMass | User | double | What is the best method to get the airmass value? ---++++ Where are the sun / moon ? |Inputs| User format | internal format | | twilight constraints | angle degrees <br/> GM: est-ce que ASTRO/NAVAL/CIVIL sont des valeurs discrites qui parlent ? | double radians | |outputs|Internal/User| Format | | sunrise sunset moonrise moonset | User | DateTime couples | Est-ce qu'il faut gerer d'autre planetes sources lumineuses ??? Quelles doit etre la precision pour les ephemerides? ---++++ Is the star still visible given to a shadowing ??? |Inputs| User format | internal format | | environment shadowing ( telescopes, mountains, building ....)| angle d'obstruction ( de 0 a 90 degres) en fonction de l'azimuth (repere a definir) | couples of Altitude / Azimuth points ( pointer ver la specification (a faire) ) | | telescope(s) min elevation | angle degree | angle radians | |outputs|Internal/User| Format | | | | | ---+++ What is the formulae of the observability given to the whole previous results? A-t'on besoin de calculer l'AirMass par station? Est-ce que la voute celeste est la meme pour toutes les stations a un meme moment? S'arrete-ton des le premier critere mauvais ou doit on faire un bilan de pertes...( par ex: une mauvaise airmass compensee par un configuration optique avec moins de pertes) Comment gere-t'on l'observalité d'une liste d'etoiles? Est simplement la juxtaposition des resultats independants ou y-a t'il des contraintes de gestion par groupe? ---++ Modelling of a source from a given interferometer TBD ---+ Various informations ---++ Station Coordinates The software handles station coordinates as described in the OIFITS (see OI_ARRAY table description). ---+++ VLTI configuration Eso defines the coordinates in an proprietary maner. The right way to get the right informations is to read the data from an AMBER oifits ( may be generated by ASPRO ). ---+++ CHARA configuration Chara expresses the station coordinates in the same format as OIFITS : TBD find URL ---++ Java astronomy libraries [[http://www.dartmouth.edu/~physics/faculty/skycalc/flyer.html][JSkyCalc = Java version of skycalc]]<br/> [[http://mhuss.com/AstroLib.html][AstroLib]]<br/> [[(URL to be defined)][PAL projet astrogrid (utilisé par APES et topcat)]] Verifier : conversion coordonnees et ephemeride (au moins soleil et lune) ---++ Various libraries * [[http://jas.freehep.org/jas3/][Java Analysis studio 3]] : advanced plot library (svg support) * [[http://svgkit.sourceforge.net/][SvgKit]] : svg generation from javascript * [[http://www.epic.noaa.gov/java/sgt/][SGT]] : Scientific Graphics Toolkit * [[http://sites.google.com/site/piotrwendykier/][Page perso pour des applications numeriques fft matrices....]] ---+ Main ASPRO functionnalities compared to alternates tools * [[http://obswww.unige.ch/~segransa/apes/usermanual.html][APES]] ---++ Observability plot In contrary to APES, ASPRO is not a planetarium (too many animations/colors).<br/> The main information consist in the observability timestamps of a target of a list of targets i.e. a simple list of time intervals could be enough (like the observation scheduler).<br/> However, beyond this minimal view the user could have details in a pop up or a contextual window (target rise/set, elevation).<br/> The user could add / remove / hide a target that is present in the plot ---++ UV coverage plot Use the Model Fitting GUI to define & display model parameters and associate a model per target instead of a single model for the current version of ASPRO.<br/> This plot could be displayed when a target is selected on the Observability plot (if possible). ---++ Other items * APES 'Select a baseline' widget has an interesting interferometer representation but it's less important. An expert mode without any configuration constraints seems a good idea * APES Paf files are specific to the PRIMA instrument and can not be reused. Only Observing blocks (OB) should be considered for ASPRO * VMT is focused on a target model and has no observability feature * Dealing with aspro setting files is an important feature to keep the user session / history * Investigate plotting libraries that provide plot interactivity (batik supports svg format with javascript support ...) 1. refresh plot with new data when the user changes anything in widgets 2. interactive plot : the user can click on the plot to get information (predefined) or run other widgets
This topic: Jmmc/Software
>
WebHome
>
JmmcASPRO
>
JmmcAsproProject
>
JmmcAsproProjectConception
Topic revision: r7 - 2009-10-01 - GuillaumeMella
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback