[NeXus-tech] NXimpatient [SEC=UNCLASSIFIED]

[HAUSER, Nick]

In response to Paul's comment about C;

The impatient (at my place) ask for code fragments for reading and writing in C, python (using h5py and pytables), C# and fortran (in that order of priority)

I agree about having examples in matlab, IDL and Igor - we have these in LAMP (IDL) and the NIST SANS (Igor) applications for some years now, so they're not a issue. 

The patient have an elegant solution in java and (hopefully by year's end) C++, using the common data model :)


Dr Nick Hauser
Computing & Electronics Group Leader
Bragg Institute. Room 1008. Building 87
Australian Nuclear Science and Technology Organisation 
Locked Bag 2001 Kirrawee DC NSW 2232 AUSTRALIA

> -----Original Message-----
> From: nexus-tech-bounces at nexusformat.org 
> [mailto:nexus-tech-bounces at nexusformat.org] On Behalf Of 
> Kienzle, Paul A.
> Sent: Wednesday, 26 October 2011 5:02 AM
> To: NeXus Technical sub-committee list
> Subject: Re: [NeXus-tech] NXimpatient
> 
> I fixed a few typos and modified the writing section to show 
> how to use h5py to read files and checked it in.
> 
> Similar examples in matlab, IDL and Igor would be useful.
> 
> I recommend moving the HDF C example to the manual in the 
> section on interacting with nexus as HDF --- the impatient 
> are not going to be programming in C.
> 
> A simple example on writing files in pure HDF would also be 
> useful, preferably using a high level api.
> 
> Meanwhile, I'm going to think a little more about the python 
> api, and whether I can leverage off the work that is already 
> in h5py and pytables.
> 
>   - Paul
> 
> ________________________________________
> From: nexus-tech-bounces at nexusformat.org 
> [nexus-tech-bounces at nexusformat.org] On Behalf Of Mark 
> Koennecke [Mark.Koennecke at psi.ch]
> Sent: Tuesday, October 25, 2011 9:38 AM
> To: NeXus Technical sub-committee list
> Subject: Re: [NeXus-tech] NXimpatient
> 
> Peter,
> 
> Peterson, Peter F. wrote:
> >
> > Mark,
> >
> > Thanks for getting this out. Unfortunately ORNL was kind 
> enough to remove the rst from your email. Could you add it to 
> svn and send out the link as to where to find it?
> >
> >
> It is already on svn, in the nexus_definitions tree, in the directory
> impatient.
> > Generally I think you are getting close, but we should 
> strive to get it shorter.
> >
> Shorter is always better but: which information shall I drop? 
> IMHO, it is
> questionable to discuss writing at all, so I would drop the 
> whole section.
> > That being said do you want this to be on the web already 
> as the "tutorial" link?
> >
> Nope, I want some internal feedback first before.
> 
> Cheers,
> 
>             Mark
> > P^2
> >
> > On Oct 25, 2011, at 6:00 AM, Mark Koennecke wrote:
> >
> >
> >> Hi,
> >>
> >> I now finished a draft version of the NeXus for the 
> Impatient Manual.
> >> I attached a pdf version of it. Please have a look. I added the
> >> restructured
> >> text sources for this to the nexus_definitions tree. Thus 
> you can fix it
> >> yourself.
> >>
> >> Best Regards and thanks again for all the good work at the 
> Code Camp,
> >>
> >>              Mark
> >>
> >> <NXImpatient.pdf>_______________________________________________
> >> NeXus-tech mailing list
> >> NeXus-tech at nexusformat.org
> >> hxxp://lists.nexusformat.org/mailman/listinfo/nexus-tech
> >>
> >
> >
> > _______________________________________________
> > NeXus-tech mailing list
> > NeXus-tech at nexusformat.org
> > http://lists.nexusformat.org/mailman/listinfo/nexus-tech
> >
> 
> _______________________________________________
> NeXus-tech mailing list
> NeXus-tech at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-tech
> _______________________________________________
> NeXus-tech mailing list
> NeXus-tech at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-tech
>