1 / 16

Purpose: Provide a User Interface for specific needs of USNO

USNO DiFX GUI . Purpose: Provide a User Interface for specific needs of USNO Run and organize repetitive DiFX jobs (daily “Intensives”, weekly R4’s, etc.) Monitor health of correlator components Non-expert operation Provide a general purpose tool for the DiFX community.

anana
Télécharger la présentation

Purpose: Provide a User Interface for specific needs of USNO

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. USNO DiFX GUI • Purpose: • Provide a User Interface for specific needs of USNO • Run and organize repetitive DiFX jobs (daily “Intensives”, weekly R4’s, etc.) • Monitor health of correlator components • Non-expert operation • Provide a general purpose tool for the DiFX community • What it Does: • Given a .vex file and some data (Mark5 module or file), produces DiFX output • Replace command line operation • Monitors hardware (processors, Mark5’s, modules) • Monitors all running jobs • Implements hardware controls (reboot, reset, etc.) 2012 DiFX Users Meeting, Sydney

  2. Operational Specifics DiFX Communication: Processor Node mk5daemon Processor Node mk5daemon Any Compute Device w/Java TCP “Head” Node USNO GUI guiServer mk5daemon UDP Multicast Network Processor Node mk5daemon Mark5 Unit mk5daemon Mark5 Unit mk5daemon 2012 DiFX Users Meeting, Sydney

  3. Operational Specifics DiFX Communication: Processor Node mk5daemon Processor Node mk5daemon Any Compute Device w/Java TCP “Head” Node USNO GUI guiServer mk5daemon Any Compute Device w/Java UDP Multicast Network USNO GUI Processor Node Any Compute Device w/Java mk5daemon USNO GUI Any Compute Device w/Java Mark5 Unit USNO GUI mk5daemon Mark5 Unit mk5daemon 2012 DiFX Users Meeting, Sydney

  4. GUI Top Level: 2012 DiFX Users Meeting, Sydney

  5. Create a New Experiment: New directory .vex file source New .vex file destination 2012 DiFX Users Meeting, Sydney

  6. Create a New Experiment: Edit .vex file content .v2d “Setup” parameters .v2d “Antenna” items 2012 DiFX Users Meeting, Sydney

  7. Create a New Experiment: Select scans by time or individually Up-to-date EOP View/Edit .v2d 2012 DiFX Users Meeting, Sydney

  8. Jobs Ready to Run: 2012 DiFX Users Meeting, Sydney

  9. Running a Job - .machines and .threads: .input and .calc editors Choose processors 2012 DiFX Users Meeting, Sydney

  10. Running a Job – Feedback from mk5daemon: 2012 DiFX Users Meeting, Sydney

  11. More Fun Things It Can Do: Passive Monitor, Database 2012 DiFX Users Meeting, Sydney

  12. More Fun Things It Can Do: Hardware Controls 2012 DiFX Users Meeting, Sydney

  13. More Fun Things It Can Do: Mark5 Modules 2012 DiFX Users Meeting, Sydney

  14. More Fun Things It Can Do: Versions, etc. 2012 DiFX Users Meeting, Sydney

  15. Work In Progress: • Make Database Work • Job Scheduler • (Real) Data Feedback • Restart where? • Plots (difx_monitor?) • Documentation • Some good, some weak, most missing • Tutorials (completely absent) • Security • Encode commands based on password • No passwords saved in setup file • Optional if you trust your network • Chase What Everyone Else Is Doing 2012 DiFX Users Meeting, Sydney

  16. Where To Get It: • Under DiFX SVN Source Tree • applications/gui/trunk • guiServer is C++ (needs to be compiled): • …/guiServer/src/guiServer [PORT#] • GUI Itself is Java “.jar” File: • java –jar …/gui/dist/gui.jar • Documentation is HTML: • …/doc/intro.html 2012 DiFX Users Meeting, Sydney

More Related