This manual incarnates in a postscript (about 25 pages),
HTML (http://www.ifh.de/~steffenp/f2000/f2000_toc.html) and in an emacs-info version.

We encourage the interested reader to look into following document:

AMANDA Software Resources and Documentation
(http://alizarin.physics.wisc.edu/amanda/datamc/resources.html)

rdmc manual
(http://www.ifh.de/baikal/software/siegmund/rdmc_toc.html)

F2000 example page
(http://www.ifh.de/~steffenp/f2000)

In case of bugs, questions, remarks, suggestions or flowers, please send them via e-mail to:
f2000@mail.ifh.de
This is a common mailing list available for discussion of AMANDA data format.

This document is free; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
Copyright (C) 1997-1999 Adam Bouchta, John Jacobsen, Predrag Miocinovic, Peter Steffen, Ole Streicher, Serap Tilav, Christopher Wiebusch (The AMANDA collaboration)

Several symbols and names occuring in this documentation and in the source are registered trademarks.

Why a common ASCII offline data format?

As announced in the Stockholm meeting (summer 1997), some of us have gotten together to forge a standard muon event format for everyone to use. While the goal is simple to state, to achieve agreement within even a small sub-group has been difficult, not to mention the actual implementation of the format in software.

The goal of the format (called F2000 in the hopes that it will be finished well before the millenium :-) ) is NOT to replace the raw data (at this time). It is, rather, to provide a flexible means to store information of use both for Monte Carloists and for the real data, from before calibration to final event selections.

We designed this new format trying to obey the following principles

• Self-consistency in units and coordinate systems, as well as some definition, in the file header, of data to follow.
• Ease of human readability without egregious expansion of file size (25% increase in compressed size relative to compressed raw data but still a significant increase compared to uncompressed raw data)
• Flexibility, thanks to user-definable additions and expandable definitions.
• Superior to previous formats, namely RAVEN and SiEGMuND. This is a must in order to justify all the re-coding work to be done on existing software.

Go to the first, previous, next, last section, table of contents.