GitLab

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11776 18c085ea-50e0-402c-830e-de6fd14e8384

points that have VTK_VERTEX entries in the conn list.


git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11775 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11774 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11773 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11772 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11768 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11764 18c085ea-50e0-402c-830e-de6fd14e8384

I made some minor changes to a couple of the scripts I use to create
a release.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11763 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11759 18c085ea-50e0-402c-830e-de6fd14e8384

adjusting logic to check long long support in PDB lite to avoid TRY_RUN and just inspect Silo version number

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11754 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11752 18c085ea-50e0-402c-830e-de6fd14e8384

1) I updated the INSTALL_NOTES for release 2.0.1.

2) I deleted the build notes. They were out of date and caused confusion
   since people would sometimes try to build visit by hand instead of using
   build_visit.

3) I updated build_visit to build visit 2.0.1.

4) I updated the release notes with my changes and cleaned them up.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11751 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11748 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11745 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11742 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11741 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11740 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11739 18c085ea-50e0-402c-830e-de6fd14e8384

I created a cron job that runs the alastor regression test suite every
night at 10:00 PM.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11738 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11737 18c085ea-50e0-402c-830e-de6fd14e8384

I renamed the makemili executable to makemili_ser so that the internal
launcher can find it when the user runs makemili.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11735 18c085ea-50e0-402c-830e-de6fd14e8384

I made some more modifications to the script that runs the regression
test suite on alastor.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11729 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11726 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11725 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11721 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11718 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11715 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11714 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11712 18c085ea-50e0-402c-830e-de6fd14e8384

I modified some of the vtk patches in build_visit to work with vtk-5.0.0f.

Eric



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11709 18c085ea-50e0-402c-830e-de6fd14e8384

I modified build_visit to use vtk-5.0.0f.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11705 18c085ea-50e0-402c-830e-de6fd14e8384

1) I modified the main CMakeLists.txt to add -DMPICH_IGNORE_CXX_SEEK
   wherever -DPARALLEL is specified to eliminate a compile failure with
   some versions of mpi. I also removed all references to the flag
   -DMPICH_IGNORE_CXX_SEEK from any makefiles that had it since it was
   no longer needed.

2) I corrected a minor error in the alastor regression suite script.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11697 18c085ea-50e0-402c-830e-de6fd14e8384

It no longer exists.

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11694 18c085ea-50e0-402c-830e-de6fd14e8384

Merged 2.0RC into trunk: Added ability to connect particle mesh based on polymer_id and particle_nid to Chombo reader. Updated config file for groening (my laptop).

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11693 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11690 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11689 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11688 18c085ea-50e0-402c-830e-de6fd14e8384

1) I added my name to the list of people to always notify if there is a
   test suite failure on alastor.

2) I deleted the config site file and host profiles for davinci.

3) I updated the script that creates the checksums for the web site to
   match what will be on the website for the 2.0.1 release.



git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11687 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11684 18c085ea-50e0-402c-830e-de6fd14e8384

git-svn-id: http://visit.ilight.com/svn/visit/trunk/src@11683 18c085ea-50e0-402c-830e-de6fd14e8384