Hello everybody!! I am trying to use Opendx to view a '.dat' file. I tried importing it into Opendx, etc. But I get a bunch of errors when I tried doing that. This is actually to view the results obtained by running a program on Fem3D, a package to solve partial differential equations. I noticed that my '.dat' file automatically got an extension '.dat.dx' on saving it in Opendx (command used: save(opendx, "filename.dat"); )....The errors that I got on trying to import the file (in "Grid or Scattered file format") are as follows:
1. 'Warning' window that says 'Socket bufsize mismatch: rcv buffer (262144 131070)' 2. 'Warning<2>' window that says 'Socket bufsize mismatch: send buffer (262144 131070)' 3. 'Message Window' window that says 'ERROR: Import: internal error: unspecified error in import' This is my second maiil regarding this very issue, and I am hoping that atleast somebody gets back to me on this. I really need help to figure this out as Opendx is totally new to me. Would really appreciate any suggestions/help provided. Thanks, best regards, Arun. --- Lloyd A Treinish <[EMAIL PROTECTED]> wrote: > > > > > Even in EPS, it's still a bitmap because that's what > Render produces. So, > the issue is independent of image format. That old > CAD package is just > translating its internal geometry to the format that > Postscript uses. > > The usual solution is just to render at high > resolution. One can use > ImageMagick convert to interpolate down to a > lower-resolution, which yields > a brute force antialiasing. > > Yes, that will require more memory. I don't use > cygwin, but every other > platform on which I have used DX, use just use > -memory n, which n is the > number of MB (memory + swap). > > There was also a posting the other day (5/18) from > Simon Spagnol of AIMS, > concerning trying to output some geometry as vector > Postscript. > > > > |---------+----------------------------------------> > | | Allen Nugent | > | | <[EMAIL PROTECTED]> | > | | Sent by: | > | | [EMAIL PROTECTED]| > | | son.ibm.com | > | | | > | | | > | | 05/13/2004 09:34 PM | > | | Please respond to | > | | opendx-users | > | | | > |---------+----------------------------------------> > > >-------------------------------------------------------------------------------------------------------| > | > > | > | To: > [email protected] > | > | cc: > > | > | Subject: Re: [opendx-users] hardcopy > graphics output > | > | > > | > > >-------------------------------------------------------------------------------------------------------| > > > > > Dear DXplorers, > > I am trying to produce nice hardcopies of my > visualisations, but I have 2 > vexing problems. > > First, I keep getting out-of-memory errors (large > arena) when I write EPS > files. The large arena is limited to 24 Mb, > apparently thanks to cygwin. > However, I don't see why this should happen when > writing EPS files of a few > > hundred kb (it seldom happened when I wrote MIFF > files of 16-frame > sequences using the same net). > > I get small-arena out-of-memory errors when I write > TIFF files of > 2 Mb, > so that avenue is out. > > Second, neither file format yields prints with > non-aliased vectors: I still > > see the staircase effect. I understand that I can't > get enough definition > with TIFF if output file size is limited to 2 Mb, > but why do I get this > with EPS? My 11-year-old DOS CAD program produces > EPS files with no > aliasing of diagonal lines! (N.B. I have set 'Allow > Rendering' and > specified 300 DPI for the EPS files.) > > Thanks in advance, > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
