1 / 14

ITER CODAC Development Environment – CODAC Core System

ITER CODAC Development Environment – CODAC Core System. Matjaz Kobal * , Csaba Gajo, Janez Golob, Takashi Nakamoto, Rok Sabjan, Klemen Strnisa , Anze Zagar, Klemen Zagar L ana Abadie, Franck Di Maio, Kirti Mahajan, Petri Makijarvi, Denis Stepanov , Nadine Utzel, Anders Wallander

sal
Download Presentation

ITER CODAC Development Environment – CODAC Core System

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. ITER CODACDevelopment Environment – CODAC Core System Matjaz Kobal*, Csaba Gajo, Janez Golob, Takashi Nakamoto, Rok Sabjan, Klemen Strnisa, Anze Zagar, Klemen Zagar Lana Abadie, Franck Di Maio, Kirti Mahajan, Petri Makijarvi, Denis Stepanov , Nadine Utzel, Anders Wallander EPICS Meeting, Aix-en-Provence, 2010-06-02

  2. Outline • Motivation • Overview • Conclusions

  3. Motivation • I&C development must follow standards (PCDH). • A long development period with many distributed partners. • Partners not familiar with ITER controll system. • ITER procedures should be easy to adopt.

  4. Solution • A common development environment. • Tools to enforce strict development procedures (SDD). • Based on EPICS and Red Hat Entrerprise Linux. • Automatic installation via RHN Satellite Server. • Documentation, training and support.

  5. Overview - Scope • File organization. • Development tools. • Unit and integration testing. • Automatic system build and testing. • Packaging and distribution procedures. • Issue tracking.

  6. Overview – File organization • Functional units. • SVN • Prescribed directory structure (Maven) • src/, doc/, target/

  7. Overview – Development tools • SDD editor • Tools are used to create new projects, compile, run, test and package the project. • Templates and step by step documentation is provided.

  8. Overview– Automatic testing • Reduce QA effort. • Problems are easily spoted. • Should be part of every unit. • Automatic tests are part of the build process.

  9. Overview– Automatic builds • Automatic build from sources in SVN. • Reduces build effort and removes human errors. • Easy to spot problems.

  10. Overview - Packaging • All code packaged in RPMs. • RHN satellite is used for package distribution.

  11. Overview– Issue tracking • Bugzilla is used to track bugs. • Bugs can be reported by all users.

  12. Overview– Web page • All CODAC information found in one place. • CODAC and EPICS documentation. • Links to infrastructure.

  13. Conclusions • Standardization of EPICS development • Simplified installation for Red Hat systems (tarball, RPMs?). • Reduced learning curve (tools and documentation) • Current version is preliminary • All cases are not yet covered. • Not all tools are graphical (CSS, Maven IDE are missing). • You can count on more useful tools from ITER.

  14. Thank You for Your Attention Come and try out CODAC Core System v1: it will make ITER and EPICS better http://www.iter.org/ORG/TEAM/CHD/CID/CODAC/Pages/CoreSystem.aspx

More Related