1 / 16

Advanced SCIRun/BioPSE Elements: GUIs, Core Libs, Contributions & Support

This documentation covers the advanced features of SCIRun/BioPSE, including GUIs, core libraries, contributions, and support for developers. It provides information on GUI elements, module synchronization, thread communication, persistent I/O, namespaces, contributing patches/modules, developer support, installation support, internal management, technical production, and external support.

mgerald
Download Presentation

Advanced SCIRun/BioPSE Elements: GUIs, Core Libs, Contributions & Support

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. Advanced SCIRun/BioPSE Elements: GUIs, Core Libs, Contributions & Support

  2. GUIs • Expose variables • Visual feedback • Module/UI • synchronization • GuiVar • tcl interpreter • $this-c [args]

  3. Threads • Intra-, inter-module parallelism • Architecture independent • pthreads • sgi threads • Inter-thread communication • mutex, barrier, mailbox • Easy to allocate/launch

  4. Persistent I/O (“Pio”) • Read/write C++ classes • Recursively descend classes • Fix pointers • Versioning for backward compatability • XDR for architecture independence • Not meant to be human-edited… no fault-tolerance!

  5. Namespaces, STL • Each Package defines its own namespace: e.g. SCIRun, BioPSE • STL used for maps, vectors, strings • iostream: std::cerr (not iostream.h)

  6. Contributing Patches • Bugzilla • Open a bug report • Return to bug report, submit attachment • Preferable to emailing scirun-develop!

  7. Contributing Modules • Same as patch, but also need… • Design spec (in XML file) • Documentation (can be in XML) • Validation net • Validation datasets • Non-conflicting license • May appear in our next code release

  8. Documentation http://internal.sci.utah.edu/developer/doc/

  9. Developer Support • Documentation • Programmer’s Guide • Module descriptions • Online code views • FAQ • Mailing List • Direct Contact • Email and Bugzilla • Network meetings (Access Grid)

  10. Installation Support • Documentation • Quick Start • Installation Guide • Third party packages • FAQ • Mailing List • Direct Contact • Email and Bugzilla

  11. Internal Management • Masterplan • Procedures and content • Module writing guide • Dynamic document • Technical Production • LaTeX, HTML, XML • Support for content providers • Online and paper forms

  12. Masterplan • Roadmap • Status report • Dynamic links

  13. Technical Production • Existing Tools • LaTeX, latex2html, DocBook (XML) • New Tools • XML DTDs, automation • Content Generation • Voice recording/recognition • Technical writer XML LaTeX HTML PDF

  14. External Support • NCRR documentation website • Updated daily • Downloaded documentation • Linked to installed release • Web based and printable docs • Submitting new documentation • Required for module submission

  15. Submitting New Docs • Format • XML • required for each module • can include complete description • template available, validation soon • LaTeX • can include complete description • template available

  16. Making Docs • Merged at doc generation time • XML and LaTeX are sources (not HTML!) • printed documentation • web documentation • Tools (soon available) • validation of XML and LaTeX • Convert XML to HTML and TeX • Convert LaTeX to HTML • LaTeX/TeX to printed documents

More Related