Re: Comments on current (3/10/06) version of BASIN

I have made some serious changes to BASIN today, please make sure to
do a fresh check out.
There were a large amount of files modified in this check in, though
most of them are minor changes. If you receive a conflict, please try
cvs diff <filename> to see if its a minor change.

The major change in this revision is that the configure and make files
no longer re-create or re-compile the swig information unless a
primary header file was changed. This should drastically improve make
times for minor changes.

Some words on a few of the things Dave mentioned yesterday:

I. Install problems, etc.
1) test.speck is in the data directory now
2) Make sure you give Jason all necessary info so that he may include
 build instructions in the documentation.

--Jason - Check out section 5.1 of the current developer manual. I
had some preliminary instructions on the modifications we made to
partiview.

II. Comments about existing structure
4) basin_local.C has waaaaay too many items in the header.

I agree. There is a new file called "libbasin.h" that the demo files
can include to handle this issue. I was going to use "basin.h" but
we already used that name for internal definitions, and it would
involve changing a lot of files already in the CVS. check out its
role in the partiview_demo.C file.

IV. Bugs
1) There are STILL some instances of the word "genvector" in functions
accessible to the user. The file "genvector.h" should be changed to
"attribute.h", and all genvectors should be changed to attributes (Jason).

Jason - I changed some of this already (Genvector.h is now
Attribute.h, along with Attribute.C), check out the latest version for
the updates. I did not change any function calls, however.

2) As you well know there is a problem with the interface between basin
and partiview, presumbly in the function:
parti.sendData(points);
when the number of points is too large. This needs to be fixed.

The basin partiview interface that is on the CVS should not be
considered ready for anything right now, testing especially. I have
made some strides in a version in my home directory, but didn't want
to check it in until we could get some tangible results.

3) There seems to be a problem with "read_speck()". Taking only the
first 100 lines of Louis's test.speck file in an attempt to do a
rudimentary test of partiview (/home/goldberg/basin/data/new.speck), I
get a crash during the read process. It is not clear why.

Uhm, not sure what you mean by only the first 100 lines, but the file you had:
/home/goldberg/basin/data/new.speck only has 100 lines.
The error you recieved was a result of the caching done in the file
loading. It should be corrected now.
Received on Tue Mar 14 12:52:37 2006