filename: image_policy Date: 2002 jul 15 originat: deh tlm: 2008 July 17 Subject: XJET policy on images. 0.0 GENERAL 1.0 FILENAMES 2.0 DOCUMENTATION 3.0 DOWNLOADING 4.0 CONTRIBUTING 0.0 GENERAL This website provides data as a public service and takes no responsibility for the integrity or quality of images. All images shall be bonafide fits files with WCS. While most images will be primary fits arrays, we realize that useful files in some cases could be edited and calibrated uv files (e.g. from the VLA) since then a user can taper to his requirements etc; or events files which have been processed (e.g. Chandra data which have been destreaked and/or had high background intervals filtered). We do not intend to duplicate existing archives. 1.0 FILENAMES While we do not aim to mandate a given system, we believe some degree of uniformity is advantageous to all. Therefore we provide the following guidelines. o lower case is preferred, but not required. Occasionally it is useful to include capital letters (like N for north instead of +). o separator: the underscore. NB: when roman characters run up against numbers, often it is not necessary to use the separator. o (1) the leading 'field' should be the source/target name (user's choice) o (2) the next 'field' should provide some sort of information about the detector or telescope: e.g. 'vla', 'cxo0000' (where '0000' is the Chandra obsid), 'HSTstis', etc. o (3) optional: some indication of the frequency (often useful for radio maps; generally not needed for X-ray maps unless the energy range has been filtered, e.g. 'soft', 'med', 'hard', or 'tot'). o (4) optional: either the obsdate in format YYmmm (e.g. 02jul, or a seriel number may be used if that makes more sense). o (5) preceeding the suffix '.fits', optionally include file type. For generic primary arrays this can be omitted, but possible uses might be 'evt2' for event files or 'flux' for maps which have been divided by the exposure map. EXAMPLES: 3c17_cxo9292__soft_flux.fits (1) (2) (3) (5) in general: name_det[obsid]_[freq]_[date]_[filetype].fits 2.0 DOCUMENTATION Each image shall have a plain ASCII text file with the basic information. This should be readable on-line, and aid users in determining if the image will be useful to them. While most of the relevent information is contained in the fits header, it is often a pain to extract. 3.0 DOWNLOADING Users are urged to copy also the corresponding document. If an image is useful to a paper, the original observer and contributor should receive acknowledgement. 4.0 CONTRIBUTING If a user wishes to contribute an image, he must: o ensure that the map is in the public domain (i.e. permission is granted by the 'owner'). o fill out the template for the doc file (a 3 minute job). o upload the image and docfile to our anonftp: sao-ftp.harvard.edu cd pub/transfer mkdir (you choose) and send us email cd (whatever) (address on website or bin harris@cfa.harvard.edu) put.....etc.... NB: If convenient, please supply a jpeg version with some indication of the angular scale.