1 / 9

Software and dataflow organization

Software and dataflow organization. Peter Roelfsema HIFI ICC manager/system engineer. AIV - ICC environment. QLA. IA tools. CUS scripts. Database. System setup. Test environment Test gets executed Data is stored in database Database is backed up daily for safety and offline use

eliora
Download Presentation

Software and dataflow organization

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. Software and dataflow organization Peter Roelfsema HIFI ICC manager/system engineer

  2. AIV - ICC environment QLA IA tools CUS scripts Database Software and dataflow organization - PRR

  3. System setup • Test environment • Test gets executed • Data is stored in database • Database is backed up daily for safety and offline use • Data not accessible outside room 50 • Note; IA only intended for quick analysis needed to verify proper test execution, not to generate analysis products • Offline environment(s) • Intended for full data analysis • SRON local installation for general use • Users can install system on their own machine as well • Updated database made available daily • Database accessible for the outside world Software and dataflow organization - PRR

  4. System configuration (control) • Test environment • Currently HCSS V 0.3.5 • Released 26th of June; HCSS build 935, HIFI build 479 • Only patches will be applied  QLA is fixed as-is • Possible upgrade dates following HCSS release schedule: HCSS V 0.3.6 – 2nd of October HCSS V 0.4.0 – ~11th of December • Offline environment(s) • SRON HCSS install is updated daily • Always the latest and greatest • Some risk of breakdown - mitigated by automatic unit testing • User release generated ~every 8 weeks • System tested  less risk w.r.t. breakdown, but not the latest and greatest • ESA has agreed to generate (a few) on-demand user builds between planned releases • Changes in system following CCB – GS common and HIFI internal • SPRs to fix existing problems • SCRs to add new functionality Software and dataflow organization - PRR

  5. Test groups • Groups per test area • Led by test engineer • Finalise test script/procedure • Verify/develop analysis tools Software and dataflow organization - PRR

  6. Development scheme • For each test • Test script(s) - CUS • Definition of generated data – building block types • Re-use building blocks wherever possible  re-use analysis tools • Analysis procedure(s) – IA applications • Data product(s) - e.g. calibration tables • Documented in • CUS scripts for HIFI FM tests – ICC/2005-021 • ILT ICC use cases – ICC/2005-005 • ILT AIV test script matrix - DRAFT Software and dataflow organization - PRR

  7. Status • All test scripts (being) analysed from beginning to end • Verify that all ingredients exist from CUS script through analysis tool • See test matrix • Tools: many basic tools available in system • QLA in place and well tested • FCU/WBS/HRS/system OK • LO TBD • HK display/analysis • Dataframe and spectrum display and basic analysis (e.g. averaging) • Pipeline components for basic HRS/WBS calibration • Heterodyne system analysis (Yfactor, Tsys, Allan variance) • Data structures • TM, dataframe, spectrum all in place, well tested • Calibration products in process of being defined • Support • ICC personnel planned to be available for SPR/SCR fixing Software and dataflow organization - PRR

  8. Status – cont. • Short functional tests • Used many times already • Require only very simple tools; HK inspection • All done (except LO?) • Functional tests • Used many times already • Require only fairly simple tools; HK inspection, data frame inspection • All done except LO • Performance/system behaviour • More advanced tools • Pipeline components available and tested • Follow up development partially available and tested • Further development needed by/with test groups Software and dataflow organization - PRR

  9. Worries • System ‘maintenance’ (HCSS re-install for EGSE, database…) • AdJ regularly needed for general AIV support • No proper HCSS/EGSE install procedure • KE now well trained in Database management • IA development – Herschel GS common • IA help needs improvement • Requires (more) system work on ESA side • HIFI committed manpower already • Distribution of IA user build • Requires system work on ESA side • No full agreement as to approach between GS users • Generally need to watch that common GS IA development does not hurt HIFI • Close attention at common groups; CCB, IA system architecture, IA user group etc. • IA development – HIFI specific • Tests groups not (yet) fully up to speed w.r.t. developing IA tasks • Next training session (4/5 September) should help • Compatibility IA developer release v.s. IA user release • Limited tool development by ICC • Manpower needed for other jobs (AIV/user support, training, HCSS system) • Unavailability of some critical manpower Software and dataflow organization - PRR

More Related