itaps-parallel Notes from today's telecon

[Onkar Sahni]

I have setup mesh adaptivity example under:
/usr/local/itaps/mesh_refinement

See /usr/local/itaps/mesh_refinement/notes/iMeshMA.README.SC08 to compile
and run (and other details).

Source code (clean version) is under:
/usr/local/itaps/mesh_refinement/src

A build is provided under:
/usr/local/itaps/mesh_refinement/build

Please try it out and let me know your comments.

Lori, Karen and Vitus, could you guys please look past "compile and run"
in the above mentioned README file, namely at the three specific iMeshP
functions that this example will focus on. I will try to plan how to
discuss on these iMeshP calls (specially for iMeshP_exchEntArrToPartsAll()
as mesh adaptivity example used it when it was not using iZoltan but now
it uses iZoltan and iZoltan makes call to this routine so I will
co-ordinate with Vitus on how to discuss this call).

Thanks,
Onkar

> Timeline:
>   - Noon CST, Thursday Nov 6: Mirror of current /usr/local/itaps being
> installed on SC machine
>   - COB CST, Friday Nov 7: All examples should be ready for trial by
> fire including instructions
>   - 11 am PST, Wednesday, Nov 12: Telecon to iron out last minute details
>   - COB Friday, Nov 14 CST: usr/local/itaps on Mesh machine will be
> mirrored and taken to SC on CD
>  - Saturday, Nov 15, Tim will email the IP address and guest account
> information so that folks
>     can log in and try their tutorial examples on new machine
>  - Sunday, Nov 16, Tutorial
>
> TODO:
>  - Create tutorial exercises and examples from current example codes;
> install in /usr/local/itaps
>      - Adaptive mesh w/ FMDB iMeshP
>      - Frontier w/ iMesh
>  - Test all examples - guinea-pigging (all)
>  - Ensure a consistent look and feel to the examples
>      - create a single document with example instructions to hand out
>  - Update web pages
>      - Doxygen comments for iMeshP (lori and karen)
>      - include .doxy on web page
>      - fix the navigation bar (lori)
>  - Draft cautionary note for READMEs indicating close contact with
> implementors a very good idea
>  - Update the tutorial slides to reflect new function names in iMeshP
>  - Update tarballs of implementations including directions for build in
> README
>  - Ensure all implementations have a consistent use of iMesh-Defs.inc;
> should be in lib directory
>  - Change directory structure on mesh machine so all tutorial examples
> in a single location
>  - Test build process for implementations using the newly created READMEs
>  - update iMesh.h and iBase.h *after* the tutorial.  Deadline of Dec 17
>
> Anything I missed?
>
>     http://www.petsworld.co.uk/guinea-pigs.htm
> <http://www.google.com/imgres?imgurl=http://www.petsworld.co.uk/images/guinea-pig.jpg&imgrefurl=http://www.petsworld.co.uk/guinea-pigs.htm&h=386&w=338&sz=18&tbnid=j_ojN5cOoncJ::&tbnh=123&tbnw=108&prev=/images%3Fq%3Dguinea%2Bpig&hl=en&usg=__FlIO52HLPRISRi4zHLfrcBtekcM=&sa=X&oi=image_result&resnum=1&ct=image&cd=1>
>
>
>