1 / 4

ANITA Software

ANITA Software. Suggested approach (suggested schedule to follow): Divide software effort into “online” and “offline” since they have different requirements for reliability, speed, implementation, etc.

Audrey
Download Presentation

ANITA Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ANITA Software • Suggested approach (suggested schedule to follow): • Divide software effort into “online” and “offline” since they have different requirements for reliability, speed, implementation, etc. • Online: daq, command, control, navigation, monitoring, telemetry, onboard CPU, ground support software, calibration • Offline: analysis, simulation, calibration, monitoring codes • Produce software requirements docs • Internal review • (N.B.: All internal reviews should be informal, but rigorous) • Produce design docs • Detailed high level design (more than a block diagram, less than full design; define interfaces) • Assign software tasks, clearly identifying responsible parties • Full design specification • Internal review • Write code for ANITA-lite (i.e., the background survey) • Rapid prototyping for online code • Perform post-mortem, make improvements • Write code for ANITA Doug Cowen/Penn State

  2. Software Design: Motherhood and Apple Pie • Choose common development environment • E.g., SourceForge, CVS,… • Use existing software tools where possible and practical • Adopt a reasonable coding standard for the chosen language(s) (use someone else’s standard to save effort) • Limit number of languages to small number (1 or 2) • C probably for front end online software • JAVA or C++ probably for the rest • N.B.: If use JAVA can piggyback on IceCube effort—an effort involving several ANITA members (Halzen, Evenson, Seckel, Woschnagg, postdocs, DFC…) Doug Cowen/Penn State

  3. Online Software • Existing DAQ software packages • MBS (from GSI, Germany; used by AMANDA & many others) • DART (from Fermilab, was called unidaq) • …and many others • Onboard CPU OSs • RTLinux* (freeware/commercial) • LynxOS (commercial) • VxWorks* (commercial) • Others… • Control Packages • Provided by NASA/NSBF • Online monitoring • DAQ packages often have built-in interfaces we can use, e.g., MBS has PAW interface • Histoscope (Fermilab) • …and many others *Has driver for Acquiris digitizer; See Beatty talk. Doug Cowen/Penn State

  4. Proposed ANITA Software Plan Division of labor: • UCI, Penn State, others join forces to work on online software • Bartol, UH, UW, others join forces to work on offline software Schedule (assuming ANITA-lite launch in 03-04, ANITA launch in 05-06): Doug Cowen/Penn State

More Related