Wiki¶

Presently, this material is organized no better than a chain of consciousness. Feel free to re-organize as necessary as well as add to it.

Meeting/Planning Notes¶

• Weekly Meeting Notes
• iField Design Notes
• Planning for iMesh to support structured grid and AMR
• Outline of Design of STL/Boost Implementation of iMesh
• Repository Reorganization Planning
• What might an ITAPS release installation look like
• 1_2_Release_Lessons
• Release Planning Suggestions
• Arrange a teleconference time with Doodle
• ITAPS discussed on HPC Podcast

Key Email Lists and Archives¶

• itaps-dev archive - for developers only
  • Note that this list is NOT advertised on lists.mcs.anl.gov
  • compose email to... itaps-dev@lists.mcs.anl.gov
• itaps-commits archive
• itaps-users archive
  • compose email to... itaps-users@lists.mcs.anl.gov
• itaps-test archive
• itaps-pis archive
  • compose email to... itaps-pis@lists.mcs.anl.gov
• List Admin

Weekly Compliance Test Results¶

iRel Discussion¶

• iRel Requirements
• iRel Interface (v1_0)
• EntArr Proposal (v1 1)
• "None" Type Proposal
• iRel Use Cases
• iRel telecon notes

Older stuff (to be reorganized)¶

• iRel 1 1 Proposal
• Tim's (putative) non-controversial issues with iRel 1 1 proposal

Python Bindings¶

PyTAPS is a set of Python bindings to the ITAPS interfaces (iMesh, iGeom, and iRel), designed to maintain the spirit of the ITAPS interfaces while taking advantage of the language features that Python provides.

• Installation instructions
• Tutorial
• Full documentation

Useful Developer Resources¶

• build_itaps primer
• steps to preparing an ITAPS release
• Wiki usage conventions for in-line commentary/discussion
• Repository Locations
  • Main Repo - https://redmine.scorec.rpi.edu/svn/itaps
  • Anon Repo - https://redmine.scorec.rpi.edu/anonsvn/itaps
• Redmine user/management guide
• SVN Manual
• SVN repo usage for trunk and release development
• Understanding SVN tree conflicts
• Language Interoperability notes
  • Simple Tutorial
  • Issues mixing C/C++ in shared and static libs
  • Mixing Fortran/C/C++
• C Pre-processor tips, tricks and best practices
• C Pre-processor tips, tricks and best practices
  • When developing code, I often use GNU CPP's #warning directive as in #warning REMEMBER TO FIX THIS so that I can annotate sections of code that still need attention. The compiler will print the text after the #warning but otherwise compile the code just fine. Better still, if the SVN repository has hooks that prevent someone from committing code with #warning directives (always a good idea since not all pre-processors support it), then it can help to prevent you from comitting code that you haven't fully developed.
• Fortran 77 for beginners
• Fortran Examples
• Notes on Fortran and ITAPS interfaces
• Steps to add new project members
• Problems on itaps.mcs.anl.gov
  • email:systems@mcs.anl.gov
  • email:raffenet@mcs.anl.gov
• Problems with redmine and/or svn repo
  • Mark Miller, miller86@llnl.gov
  • Tim Wickberg, wickbt@rpi.edu
• Redmine user for itaps-dev email
  • miller86-itaps-dev