A .dx file has necessary header information and may also include the data itself.
Or, the .dx file can be just header info and contain file references (pointers if you will) to the files that contain the actual data. These are usually suffixed .dat or .bin (ascii or binary), but that's completely arbitrary, as a .dx file can just as easily point to a .txt or .foobar file if you want it to.
So set up a really simple little test mesh and try exporting. You should be able to open the .dx file with any text editor to inspect that somewhere near the end, there is a 'field' declaration. Without that, it's unlikely you have a valid importable file. If FEM3D is not exporting a .dx file, you have a different problem.
Import assumes that a file called baz.dx really is a .dx file, but if it isn't, bad things happen (like no import). So you can name any file baz.dx but that won't make it a .dx file. If that .dat file that FEM3D is exporting is not really a .dx file, it won't work.
Then whine to FEM3D about their lousy exporter (with which I have no experience, so I'm joking (:-) ).
On Monday, May 24, 2004, at 21:23 America/New_York, Arun Viswanathan wrote:
Hi David,_______________________________
I tried seeing what's in the file, it seems to be
empty?! The file is called "p1.dat.dx". I wrote a
program taking help from an example (in the Fem3D
manual), I used the command "save(opendx, "p1.dat",
M)" to save the program's result in it (M is a mesh
used in the code). Do you think there could be a
problem in the way I am saving, or have I used the
wrong extension?? Please tell me what is wrong, cause
I am stumped and really need help.
Thanks, best regards,
Arun.
--- David Thompson <[EMAIL PROTECTED]> wrote:
The bufsize mismatch is just a warning and can be.............................................................................
ignored. It is some
code that lets you know that socket bufsize's are
not matching but
does not cause any kind of error message.
The problem you are having with Import is relative
to the 3rd message
you report "ERROR: Import: internal error:
unspecified error in
Import"
Is your data file really a dx file? What does the
first line in the
file look like?
David
--
David L. Thompson Visualization(406)756-7472
and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway
Drive, Missoula, MT 59804
Phone :
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
Chris Pelkie
Scientific Visualization Producer
622 Rhodes Hall, Cornell Theory Center
Ithaca, NY 14853
