Although the data model allows arrays to be any type, including positions, modules that operate specifically on positions requires them to be floats. You should have locations in your general array import specification be float.
"McGee" <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 02/06/2001 12:59:02 PM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: <[email protected]> cc: Subject: RE: [opendx-users] 3D Scatter Data Problem ~ maybe a bug in DX Hi Chris Very interesting, it sounds like the variable declaration in the source code declares the positions and data has floats, however the user has the option to use double. : ] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chris Pelkie Sent: Tuesday, February 06, 2001 8:05 AM To: [email protected] Subject: RE: [opendx-users] 3D Scatter Data Problem ~ maybe a bug in DX >Hi Chris and David > >I used AutoRegrid on my 3D Scatter data and got a very nice result. I went >back and tried 100 points as you suggested Chris, but still have this >warning about duplicated position. I went through the ASCII data file but >could not find anything strange in the file. > >Cheers > >Bruce > > >Nevertheless, that makes them unique. But.. that doesn't matter cause DX >will happily plot coincident positions. So I'll go David one better: make >both type declarations double as the data I just reread my note and see I said "make double" when of course I meant "make both float". If indeed, you are getting a "Warning", just ignore it. It's the Black Errors that bring processing to a halt that one has to deal with. I was thinking that if the general file parser is "overreading" doubles, it might have been running off the end of the file as it consumed floats. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED]
