itaps-parallel tutorial comments
txie at scorec.rpi.edu
txie at scorec.rpi.edu
Wed Nov 5 17:09:31 CST 2008
Hi Martin and Vitus,
Please see my comments below. Thanks.
> hello vitus,
>
> i just tried out your tutorial. works great .. i had just a few
> hickups (see below)! i think your "Zoltan" would be a good fit after
> "Hello" and before "Smooth". Maybe you could create a single directory
> for the two exercises similar to the structure of "Hello" and "Smooth" ?
>
> below are my comments for the two tutorials
>
> cheers
>
> martin
>
> ------------
>
> comments for tutorial1
> ======================
>
> - in EXERCISE 3 it took me while to figure out to use argv[2]
>
> - when i type 'make' it wrongly tells me
>
> "To build the iMeshPZoltan C++ test program, type
> gmake ZOLTAN_ARCH=desired_arch fmdbzoltan"
>
> - you should add the following variables to EXCERCISE 4 unless you
> left them out on purpose
>
> int parts_size, parts_allocated = 0;
>
> - in the Hands_on file it should say to run. not the added './'
>
> mpirun -np 4 ./fmdbzoltan 4 part.sms REGION tmp
>
> comments for tutorial2
> ======================
>
> - change comment "delete the partition" to "destroy the partition"
>
> - change comment "delete the part" to "destroy the part"
>
> - if the user does not use "VTK" as option in iMeshP_saveAll and then runs
>
> mpirun -np 4 ./fmdbzoltan 4 part.sms REGION repart
>
> the code crashes. instead the user should call
>
> mpirun -np 4 ./fmdbzoltan 4 part.sms REGION repart.sms
Yes. FMDB does this filename checking when it writes out mesh in
parallel. If this is a problem, I can modify it soon. And I will also
check the iMesh_save() function to make it consistent. Thanks.
>
> which will work either way.
>
>
>
>
More information about the itaps-parallel
mailing list