Tags:
view all tags
%TOC% ---++ Purpose The OI-FITS (Optical Interferometry Flexible Image Transport System) format is commonly used to store data provided by optical interferometers. This software package is intended to check the validity of OI-FITS files relative to IAU standard. The software package is intended to provide information about an input file, especially if this one isn't compliant with the norm, with different levels of granularity. ---++ Technical information about OI-FITS format. See the following articles or documents: * [[http://www.cv.nrao.edu/fits/][FITS format definition]] * [[http://www.mrao.cam.ac.uk/research/OAS/oi_data/oifits.html][OIFITS format definition]] * [[http://www-laog.obs.ujf-grenoble.fr/doc/AMBER/public/VLT-SPE-AMB-15830-3984.pdf][AMBER product data specification]] ---++ OI-FITS format controller This tool aims at checking OI-FITS files format validity. ---++ Requirements ---+++ Software perspective The OI-FITS format controller software is intended to be provided as * a program runable in standalone mode * a program operable on common platforms (ie Windows, Mac OS X, Linux) * function library (?? or program ??) which can be integrated in a user's program ---+++ General requirements The software has to provide a command line interface (CLI) and a graphical user interface (GUI). Both will allow the user * to select one or more input files. * to configure the tool according to specific expectations (TBD - lesquelles sont possibles exactement?? ). * to access detailed information about detected irregularities. * anything else??? ---+++ Constraint requirements relative to the format itself ---++++ CR-01 Mandatory binary tables The following tables and their occurance are strictly defined in the standard. These tables are the ones with an extension name beginning with =OI_=. * OI_TARGET (one and only one) * OI_WAVELENGTH (one or more) * OI_ARRAY (one or more) And one or more of the following ones: * OI_VIS * OI_VIS2 * OI_T3 Additional binary tables may appear in the file, provided their extension names do not begin with =OI_=. ---++++ CR-02 =OI_*= tables content =OI_*= tables mandatory keywords and columns names, formats and units are described in IAU document. None of them can be missing, but others can be added. ---++++ CR-03 Cross referencing Cross referencing identifiers must be unique (eg: Each OI_WAVELENGTH table in a file must have a unique value for INSNAME).
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r11
|
r9
<
r8
<
r7
<
r6
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r7 - 2008-03-18
-
GuillaumeMella
Home
Site map
Jmmc web
Faq web
ProspectiveHRA2014 web
Software web
VltiSchool2010 web
VltiSchool2013 web
VltiSchool2015 web
VltiSchool2018 web
Main web
Sandbox web
DeuxiemePage web
TWiki web
Software Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Register User
Edit
Attach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback