NIAC2011 CodeCamp

 logo for the 2011 NeXus Code
Camp

Purpose

Develop NeXus software components through intense effort by small groups working on specific projects and tasks. It is expected that those attending the 2011 NeXus Code Camp will already have strong foundation and understanding in aspects of the NeXus software and come ready with knowledge, tools, and ideas to make significant progress during the event. The specific projects and tasks, as well as the list of participants, are described on this wiki and will be revised as the event draws near.

See previous NeXus Code Camps:

Dates

Daily Agenda

Meeting room is Building 401, Room B2100

Thursday, 2011 October 20

time description comments
9:00 - 10:15 AM meeting organize slate of projects and tasks
10:15 - 10:45 AM morning break (included)
10:45 AM - 12:00 PM meeting work on projects and tasks
12:00 - 1:15 PM Comparison of APS Data_Exchange+HDF5 for Tomography with NeXus+HDF5 (*) working lunch onsite, hosted by APS, 401/B2100
1:15 - 3:15 PM meeting work on projects and tasks
3:15 - 3:30 PM afternoon break (included)
3:30 - 5:00 PM meeting work on projects and tasks
5:00 - 6:00 PM meeting daily summary (plenary)

(*) speakers for the working lunch include:

Friday, 2011 October 21

time description comments
9:00 - 10:15 AM meeting work on projects and tasks
10:00 - 10:30 AM morning break (included)
10:30 AM - 11:30 PM The Current State of NeXus public talk, 401/A1100
12:00 - 1:15 PM lunch offsite, traveler’s expense
1:15 - 3:15 PM meeting work on projects and tasks
3:15 - 3:30 PM afternoon break (included)
3:30 - 5:00 PM meeting work on projects and tasks
5:00 - 6:00 PM meeting daily summary (plenary)

Saturday, 2011 October 22

time description comments
9:00 - 10:15 AM meeting work on projects and tasks
10:15 - 10:45 AM morning break (included)
10:45 AM - 12:00 PM meeting work on projects and tasks
12:00 - 1:15 PM lunch offsite, traveler’s expense
1:15 - 3:15 PM meeting work on projects and tasks
3:15 - 3:30 PM afternoon break (included)
3:30 - 5:00 PM meeting work on projects and tasks
5:00 - 6:00 PM meeting Code Camp wrap-up (plenary)

Planning

Business Matters

Since this is not to be a meeting of the full NIAC, no business matters can be resolved.

Projects and Tasks

These items are sorted in order of priority that they be finished. Only items that currently exist in the project plan are being worked on.

  1. move to using 1.8 version of HDF5 API (would allow HDF5 transparent external linking)
  2. NXclonehandle
  3. PyTree API
  4. discuss axes for multi dimensional scans
  5. discuss axis dependency encoding
  6. discuss and decide switch to CMake for building NeXus
  7. discuss and decide on the use of sphinx for documentation
  8. Design NXdict replacement based on NXDL
  9. Improve nxvalidate
  10. Link NeXus WWW-site with docbook manual
  11. A Fedora installer
  12. Discuss and write NeXus for the Impatient
  13. Cleanup NeXus applications

Other Tasks

Items not currently on the project plan, but have arisen recently:

  1. support for more than one unlimited array dimension (http://trac.nexusformat.org/code/ticket/258)
  2. support larger dataset dimensions (currently dimensions are “int” so overflow at > 2^31 elements)

Presentations

  1. presentation about cmake (Freddie Akeroyd or Pete Peterson)
  2. about sphinx for documentation (Pete Jemian) 
PDF
  3. about parallel HDF (Mark Koennecke, anyone else with more experience?)
  4. assessment of work to migrate from HDF 1.6 to HDF 1.8 (Freddie Akeroyd)
  5. public talk: The Current State of NeXus, Building 401, Room A1100, Friday, Oct. 21, 10:30 - 11:30 AM

Schedule

Meeting room is Building 401, Room B2100

Here is the daily schedule (tentative):

time description comments
9:00 - 10:15 AM meeting work on projects and tasks
10:15 - 10:45 AM morning break (included)
10:45 AM - 12:00 PM meeting work on projects and tasks
12:00 - 1:15 PM lunch offsite, traveler’s expense
1:15 - 3:15 PM meeting work on projects and tasks
3:15 - 3:30 PM afternoon break (included)
3:30 - 5:00 PM meeting work on projects and tasks
5:00 - 6:00 PM meeting daily summary (plenary)

Notes:

  1. late-afternoon wrap-up (plenary) each day
  2. morning and afternoon breaks will be included in amenities charge
  3. breakfast, lunch, dinner will be in a local restaurant at traveler’s expense

Practical Matters

Registration

Step 1: Register with the APS as a visitor to start the process.
Step 2: Send an email to jemian@anl.gov announcing your plan to attend.

APS Visitor registration

web site: https://www.aps.anl.gov/About/Visiting/visitor_registration.php

You must register as an APS Visitor in advance (to identify matters related to Passport, Visa, and ANL Site Access) or you should not expect access to the ANL site. If asked, indicate that you are visiting Pete Jemian.

For the paperwork of all international visitors, we need each degree, year earned, and institution name. Additionally for certain visas, we need additional information:

F1 visa: we need the I-20 number and expiration date.
J1 visa: we need the DS-2019 number and expiry date.
H1 visa: we need the I797 number and expiry date.

Venue

Argonne Guest House
Argonne National Laboratory
9700 S. Cass Avenue - Building 460
Argonne, IL 60439
USA

Please reserve your own rooms directly with the hotel:

Web site: http://www.anlgh.org/
telephone: +1 - 800-632-8990, +1 - 630-739-6000
fax: +1 - 630-739-1000
map link: http://maps.google.com/maps?q=Argonne+Guest+House&hl=en&ll=41.708228,-87.985897&spn=0.024798,0.049953&sll=37.0625,-95.677068&sspn=27.008217,51.152344&t=h&z=14

Directions and Maps

Host

Costs

Equipment

item quantity who provides?
projector & screen   host
LCD displays, keyboards, & mice   host
120 VAC, 60 Hz, US-style 3-prong extension cords sufficient host
foreign electrical power adapter as needed traveler
Wi-Fi connections sufficient hotel

Participants

participant affiliation arriving departing registration? ANL gate pass?
Pete Jemian APS host host host host
Mark Könnecke PSI 2011-10-18 2011-10-24 complete yes
Tobias Richter Diamond 2011-10-19 2011-10-25 complete yes
Eugen Wintersberger DESY 2011-10-19 2011-10-23 complete yes
Freddie Akeroyd ISIS 2011-10-19 2011-10-23 complete yes
Peter Peterson SNS 2011-10-19 2011-10-22 complete yes
Ray Osborn MSD/ANL 2011-10-20 2011-10-22 N/A yes
Paul Kienzle NCNR/NIST 2011-10-19 2011-10-23 ? pending
           

Presentations

… coming …

Final Report

As some of you might know, the NeXus technical subcommittee and especially Pete Jemian have invested a lot of work to update the NeXus manual in the last year. It is now current and much better then it used to be. In this work we arrived at a major milestone on our last code camp in Chicago, October 20 - 22. Now, the NeXus WWW site has received a new front page and its content is created from the NeXus manual. Though not all of it looking as beautiful as it could be, at least the content is correct and up to data.

Another good news is that we had some discussions with the detector manufacturer Dectris. They do the Mythen, Pilatus and Eiger detectors. With the Eiger detector they will start writing HDF-5 files with NeXus conventions. The programming model will be that Dectris writes the detector data and the local DAQ system adds further meta data to the HDF-5 NeXus file. In order to support this, some more fields have been added to NXdetector.

Other things which we addressed during the code camp:

All in all, we managed to put a man-month of work into NeXus between the seven of us who attended the code camp. Many thanks to everyone who participated and to Pete Jemian who did a wonderful job as a local organiser. [PRJ: I thank all of you.]

We are in good hope that a new version of the NeXus-API will be released before the end of this year. We also strive to make a 1.0 release of the NeXus application definitions by then.

Best Regards, Mark Koennecke

Added note

We also has a good discussion with scientists and staff of the APS regarding the release of details of how NeXus is implemented in HDF5. Also discussed were current APS plans to store data in HDF5 files but, for performance reasons as well as simplicity, not necessarily in compliance with NeXus.