comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » "standard" ASCII file format
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
"standard" ASCII file format [message #10557] Tue, 16 December 1997 00:00 Go to next message
Thomas Egi is currently offline  Thomas Egi
Messages: 1
Registered: December 1997
Junior Member
Hi everyone,

in the field of electric circuit simulation there is an "industriy
standard" for simulation output called CSDF (common simulation data
format), which can be read by all of the visualization tools. Is there a
corresponding "de facto standard file format" for data import in the
world of pv-wave or IDL? And if so, where can I get information on that?

Thank you for any hints

Thomas
Re: "standard" ASCII file format [message #10674 is a reply to message #10557] Thu, 18 December 1997 00:00 Go to previous message
LC's No-Spam Newsread is currently offline  LC's No-Spam Newsread
Messages: 18
Registered: September 1997
Junior Member
On Tue, 16 Dec 1997, Thomas Egi wrote:

> in the field of electric circuit simulation there is an "industriy
> standard" for simulation output called CSDF (common simulation data

I believe every field has its own standards.
For instance in astronomy the standard for transport of image data is
FITS (basic FITS). The de facto standard for transport of other data
is a set of extension to FITS (which unfortunately are too flexible and
relaxed to be an unique standard ... let's say they ensure interoperability
more than portability).

On the other hand what is a great thing for *transport* may not be a
great thing as work format. Most astronomical packages therefore convert
into a native format (OS dependent, that's often more efficient). I have my
own too.

> corresponding "de facto standard file format" for data import in the
> world of pv-wave or IDL? And if so, where can I get information on that?

The advantage of IDL is that is is not a package but a language, and
can be adapted very flexibly to import any kind of data (whose format
is documented). E.g. I know there is an "astrolib" to read FITS, and
I have my own little set of routines to read my own format.

I've also been told by a colleague that one can save an IDL session
under a given OS, move the saved binary file to a different OS, restore
it and continue working as one just resumes the session. But probably
this is barely relevant to the present issue.

------------------------------------------------------------ ----------
nospam@ifctr.mi.cnr.it is a newsreading account used by more persons to
avoid unwanted spam. Any mail returning to this address will be rejected.
Users can disclose their e-mail address in the article if they wish so.
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: IDL verses other interpertative languages (tcl/tk, khouros, pv_wave, etc).
Next Topic: Free source code diagramming software offerred

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 16:00:57 PDT 2025

Total time taken to generate the page: 0.00530 seconds