From noreply at nexusformat.org  Fri Jan  2 18:27:32 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 02 Jan 2009 18:27:32 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #144: IDL build problem
In-Reply-To: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
References: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
Message-ID: <062.f05c8fec9f00d939dcbc0d5cf1d229d0@nexusformat.org>

#144: IDL build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Stuart Campbell
      Type:  defect          |      Status:  closed         
  Priority:  minor           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  4.2rc2         
Resolution:  fixed           |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Stuart Campbell):

 I've set this to closed, but could you give a test Mark ?

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/144#comment:4>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Sat Jan  3 22:42:10 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Sat, 03 Jan 2009 22:42:10 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #146: IDL Bindings fail to build
	on Mac OS X
Message-ID: <054.0a0ed045d775c0dbf0b7ee497621e571@nexusformat.org>

#146: IDL Bindings fail to build on Mac OS X
-----------------------------+----------------------------------------------
 Reporter:  Stuart Campbell  |       Owner:  Unassigned     
     Type:  defect           |      Status:  new            
 Priority:  minor            |   Milestone:  NeXus 4.2 Ready
Component:  bindings         |     Version:  4.2rc2         
 Keywords:                   |  
-----------------------------+----------------------------------------------
 There is a hard coded path that contains "linux" - which needs to be
 "darwin" on OS X.
 Also, unlike Linux, in which ITT has labeled the 32-bit directory
 bin.linux.x86 on a Mac, they call it bin.darwin.i386!

 We may need to allow people to choose whether to build the 32 or 64
 bindings on a Mac as both libraries are there in IDL.  (We may also have
 the same problem on Linux)

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/146>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 12 15:47:06 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 12 Jan 2009 15:47:06 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #147: Configure and tests do not
	set LD_LIBRARY_PATH
Message-ID: <054.8169b8f76b5e8f2ef543d18ffafea566@nexusformat.org>

#147: Configure and tests do not set LD_LIBRARY_PATH
-----------------------------+----------------------------------------------
 Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd  
     Type:  defect           |      Status:  new              
 Priority:  major            |   Milestone:  NeXus 4.2 Release
Component:  napi             |     Version:  4.2rc2           
 Keywords:                   |  
-----------------------------+----------------------------------------------
 This means they may either fail to pick up the hdf5 library or pick up an
 old NeXus library

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/147>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 12 15:48:50 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 12 Jan 2009 15:48:50 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #147: Configure and tests do
	not set LD_LIBRARY_PATH
In-Reply-To: <054.8169b8f76b5e8f2ef543d18ffafea566@nexusformat.org>
References: <054.8169b8f76b5e8f2ef543d18ffafea566@nexusformat.org>
Message-ID: <063.c83d5bbf1b198861b1cba19d8bdda358@nexusformat.org>

#147: Configure and tests do not set LD_LIBRARY_PATH
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd  
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1142]) Set LD_LIBRARY_PATH during configure and when running tests.
 Refs #147.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/147#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 12 16:27:41 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 12 Jan 2009 16:27:41 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #147: Configure and tests do
	not set LD_LIBRARY_PATH
In-Reply-To: <054.8169b8f76b5e8f2ef543d18ffafea566@nexusformat.org>
References: <054.8169b8f76b5e8f2ef543d18ffafea566@nexusformat.org>
Message-ID: <063.6a5f6babeedec4315835cf922ec5da10@nexusformat.org>

#147: Configure and tests do not set LD_LIBRARY_PATH
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd  
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1143]) Move LD_LIBRARY_PATH setting to TEST_ENVIRONMENT. Refs #147.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/147#comment:2>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 12 16:47:36 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 12 Jan 2009 16:47:36 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.8f6e5d2697cf546b25feca51677c89ff@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1144]) Merge in changes from trunk  r1141:r1143 r1136:r1139
 * XML fixes
 * fixes for LD_LIBRARY_PATH
 Refs #115.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:8>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 12 22:06:39 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 12 Jan 2009 22:06:39 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #148: Tool to build and add the
 file tree structure into the file.
Message-ID: <054.00dcab85e0d2e396533bd54a02e139cd@nexusformat.org>

#148: Tool to build and add the file tree structure into the file.
-----------------------------+----------------------------------------------
 Reporter:  Stuart Campbell  |       Owner:  Stuart Campbell
     Type:  enhancement      |      Status:  new            
 Priority:  minor            |   Milestone:  NeXus 4.3 Ready
Component:  applications     |     Version:  trunk          
 Keywords:                   |  
-----------------------------+----------------------------------------------
 It would be useful (for the case of large files) to have the tree
 structure of the file stored within the file as it can take minutes just
 to do a tree walk of the file.

 I am going to develop a command line tool to parse the file, and create an
 NXnote (called $ENTRYNAME_tree) at the top level for each NXentry that
 contains just a list of paths and class names.

 This will go into the contrib/applications directory.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/148>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 12 22:09:48 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 12 Jan 2009 22:09:48 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #148: Tool to build and add
 the file tree structure into the file.
In-Reply-To: <054.00dcab85e0d2e396533bd54a02e139cd@nexusformat.org>
References: <054.00dcab85e0d2e396533bd54a02e139cd@nexusformat.org>
Message-ID: <063.c4dd63292978a798645ee09ec6c5dfcd@nexusformat.org>

#148: Tool to build and add the file tree structure into the file.
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Stuart Campbell
      Type:  enhancement      |      Status:  new            
  Priority:  minor            |   Milestone:  NeXus 4.3 Ready
 Component:  applications     |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Stuart Campbell):

 (In [1145]) created directory. refs #148

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/148#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 14:19:50 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 14:19:50 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
Message-ID: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>

#149: python test script fails with hdf4 and xml
-----------------------------+----------------------------------------------
 Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
     Type:  defect           |      Status:  new              
 Priority:  major            |   Milestone:  NeXus 4.2 Release
Component:  napi             |     Version:  4.2rc2           
 Keywords:                   |  
-----------------------------+----------------------------------------------
 python nxstest.py hdf5   works OK, but both   python nxstest.py hdf4   and
 python nxstest.py xml   fail

 I've now added the python test to the usual "make check" and it will
 appear in the next commit and 4.2 branch kit

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 14:20:21 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 14:20:21 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.76a9c24d74ed889c494a6f7c72d2c1a6@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1146]) Add puython test script to usual tests run. Refs #149.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 14:52:54 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 14:52:54 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.1c1a7ec6740f98203c8aae1d33847975@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1147]) Remove data files created by python test. Refs #149.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:2>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 14:56:42 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 14:56:42 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.6ad101eb6f791723428a0e190f0ff2ed@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1148]) Update trunk with 4.2 changes for python tests. Refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:9>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 15:37:50 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 15:37:50 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #150: python bindings do not
	install properly
Message-ID: <047.8b97debb68b2545f455a71b19038f768@nexusformat.org>

#150: python bindings do not install properly
----------------------+-----------------------------------------------------
 Reporter:  Cpascual  |       Owner:  Unassigned       
     Type:  defect    |      Status:  new              
 Priority:  major     |   Milestone:  NeXus 4.2 Release
Component:  bindings  |     Version:  4.2rc2           
 Keywords:            |  
----------------------+-----------------------------------------------------
 After compiling and installing nexus-4.2rc2, the python bindings get
 installed as follows:
 [BR]
 <.../site-packages>/nexus/nxstest.py [[BR]]
 <.../site-packages>/nexus/nxs/napi.py[[BR]]

 Which is a problem because:[[BR]]
 a) missing {{{__init__.py}}} [[BR]]
 b) installs to "nexus/nxs" instead of "nxs"  [[BR]]
 c) copies unnecesary non-module nxstest.py in site-packages[[BR]]

 Consequence: one cannot do "import nxs" as indicated in the NEXUS Python
 API.

 IMHO, the correct installation structure should be like that created by
 the previously available distutils script:[[BR]]
 <.../site-packages>/nxs/napi.py[[BR]]
 <.../site-packages>/nxs/{{{__init__.py}}}[[BR]]

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/150>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 16:39:23 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 16:39:23 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #150: python bindings do not
	install properly
In-Reply-To: <047.8b97debb68b2545f455a71b19038f768@nexusformat.org>
References: <047.8b97debb68b2545f455a71b19038f768@nexusformat.org>
Message-ID: <056.bd31044fc5d0758a70a096fbdafb63ef@nexusformat.org>

#150: python bindings do not install properly
-----------------------+----------------------------------------------------
  Reporter:  Cpascual  |       Owner:  Unassigned       
      Type:  defect    |      Status:  new              
  Priority:  major     |   Milestone:  NeXus 4.2 Release
 Component:  bindings  |     Version:  4.2rc2           
Resolution:            |    Keywords:                   
-----------------------+----------------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1149]) Fix python install directory. Refs #150.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/150#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 16:41:56 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 16:41:56 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.579dd1e499d7b6db94c245d285918d0f@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1150]) Update trunk with 4.2 branch fix for python install path. Refs
 #115.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:10>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 16:46:17 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 16:46:17 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #143: rank not set properly by
	analyzeDim
In-Reply-To: <054.c146a0720936db0c0e7408994616246b@nexusformat.org>
References: <054.c146a0720936db0c0e7408994616246b@nexusformat.org>
Message-ID: <063.6b31d8c58822a0c60135c29dd9a8c2fd@nexusformat.org>

#143: rank not set properly by analyzeDim
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd  
      Type:  defect           |      Status:  closed           
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:  fixed            |    Keywords:                   
------------------------------+---------------------------------------------
Changes (by Freddie Akeroyd):

  * status:  new => closed
  * resolution:  => fixed

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/143#comment:3>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 16:47:06 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 16:47:06 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #147: Configure and tests do
	not set LD_LIBRARY_PATH
In-Reply-To: <054.8169b8f76b5e8f2ef543d18ffafea566@nexusformat.org>
References: <054.8169b8f76b5e8f2ef543d18ffafea566@nexusformat.org>
Message-ID: <063.ec76c69165753f873855f98dd74b912a@nexusformat.org>

#147: Configure and tests do not set LD_LIBRARY_PATH
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd  
      Type:  defect           |      Status:  closed           
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:  fixed            |    Keywords:                   
------------------------------+---------------------------------------------
Changes (by Freddie Akeroyd):

  * status:  new => closed
  * resolution:  => fixed

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/147#comment:3>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 17:20:22 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 17:20:22 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #142: CPP headers not installed
In-Reply-To: <054.99a591033ccddac90139c88b46e06126@nexusformat.org>
References: <054.99a591033ccddac90139c88b46e06126@nexusformat.org>
Message-ID: <063.f45e18b731327b7c359a9973a46b8259@nexusformat.org>

#142: CPP headers not installed
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Unassigned       
      Type:  defect           |      Status:  closed           
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  bindings         |     Version:  4.2rc2           
Resolution:  fixed            |    Keywords:                   
------------------------------+---------------------------------------------
Changes (by Freddie Akeroyd):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 (In [1151]) Install CPP headers. Fixes #142.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/142#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 13 17:25:11 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 13 Jan 2009 17:25:11 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.1ecd403096c03c00ebfccd385bed080c@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1152]) Update trunk with 4.2 branch change for installing headers.
 Refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:11>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 09:43:57 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 09:43:57 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
Message-ID: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>

#151: IDL-API dumping core, Build problem
----------------------------+-----------------------------------------------
 Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
     Type:  defect          |      Status:  new            
 Priority:  major           |   Milestone:  NeXus 4.2 Ready
Component:  bindings        |     Version:  4.2rc2         
 Keywords:                  |  
----------------------------+-----------------------------------------------
 Using the IDL-API causes IDL to dump core on Linux.

 Moreover there is still a build issue: the build process builds a
 libNeXusIDL-API.so in the
 .libs directory. For reasons in IDL the library has to be called NeXus-
 IDL-API.so. This must
 be same as the dlm file.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 09:45:34 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 09:45:34 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.7813c41c4d06b3dc821ded87cbfd2263@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Mark Koennecke):

 (In [1153]) - Fixed core dumps caused by IDL-API, refs #151

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 10:07:23 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 10:07:23 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.752a5495e4cae8d88aa4cb75ffd2ed75@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Mark Koennecke):

 I fixed most of this. The cause was some dodgy code for dimension handling
 which worked under SL3
 but did not under SL5. Now at least the self test runs. There are still
 issues:
 - The IDL API has to be built with the -fno-strict-aliasing option of gcc.
 Otherwise there will be
   core dump. BTW: this problem may affect all code using NXmalloc. It is
 triggered by casts like
   (char **) used often with NXmalloc. Gcc alerts you to the problem
 through obscure warnings like:
   type punned pointer breaks strict aliasing
   Depending on your installation of gcc strict aliasing may be switched on
 or not.
 - Writing compressed data with HDF-4 does not work. HDF4 fails to
 initialize the compression  library. This what HEprint tells me. The rest
 of the NeXus tests run fine, so I conclude that my
 libraries are fine. I tried to link NeXusIDL-API.so statically with a
 known good libz.a. This did
 not help. I assume that the problem is that there is a bad libz linked
 statically into IDL.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:2>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 13:48:53 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 13:48:53 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #152: Library for IDL bindings has
	the wrong name.
Message-ID: <054.cc566b61bb0d632b18dc1b5a69499d5d@nexusformat.org>

#152: Library for IDL bindings has the wrong name.
-----------------------------+----------------------------------------------
 Reporter:  Stuart Campbell  |       Owner:  Unassigned     
     Type:  defect           |      Status:  new            
 Priority:  major            |   Milestone:  NeXus 4.2 Ready
Component:  bindings         |     Version:  4.2rc2         
 Keywords:                   |  
-----------------------------+----------------------------------------------
 The library that is built for the IDL bindings is called {{{libNeXusIDL-
 API.*}}} but it needs to be called {{{NeXusIDL-API.*}}}.  This is because
 the library needs the same name as the {{{.dlm}}} file.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/152>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 15:45:37 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 15:45:37 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.61250bd7ce9338b566e17d99df109154@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1154]) Merge in Marks changes from trunk to 4.2 branch. Refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:12>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 16:37:47 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 16:37:47 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #153: Allow the use of MacPorts
Message-ID: <054.cf30bcc74b47ea1503f1ee4964c1ca23@nexusformat.org>

#153: Allow the use of MacPorts
-----------------------------+----------------------------------------------
 Reporter:  Stuart Campbell  |       Owner:  Unassigned
     Type:  enhancement      |      Status:  new       
 Priority:  major            |   Milestone:            
Component:  napi             |     Version:  trunk     
 Keywords:                   |  
-----------------------------+----------------------------------------------
 Allow people to be able to use MacPorts instead of fink if they wish.
 This basically means adding {{{/opt/local}}} to the search path for HDF.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/153>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 16:37:56 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 16:37:56 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #153: Allow the use of MacPorts
In-Reply-To: <054.cf30bcc74b47ea1503f1ee4964c1ca23@nexusformat.org>
References: <054.cf30bcc74b47ea1503f1ee4964c1ca23@nexusformat.org>
Message-ID: <063.ffddb03cbf94724bac3918df11b015db@nexusformat.org>

#153: Allow the use of MacPorts
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Stuart Campbell
      Type:  enhancement      |      Status:  assigned       
  Priority:  major            |   Milestone:                 
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Changes (by Stuart Campbell):

  * owner:  Unassigned => Stuart Campbell
  * status:  new => assigned

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/153#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 16:39:36 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 16:39:36 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #152: Library for IDL bindings
	has the wrong name.
In-Reply-To: <054.cc566b61bb0d632b18dc1b5a69499d5d@nexusformat.org>
References: <054.cc566b61bb0d632b18dc1b5a69499d5d@nexusformat.org>
Message-ID: <063.a78ea345413909b3d87ad13532a9bc68@nexusformat.org>

#152: Library for IDL bindings has the wrong name.
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Unassigned     
      Type:  defect           |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  bindings         |     Version:  4.2rc2         
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1155]) Add in --enable-32bit
 Fix IDL library install name
 refs #152

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/152#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 16:43:41 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 16:43:41 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.e9deee5a5bd2efbb2b455ac6a61139e1@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1156]) refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:13>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 16:52:11 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 16:52:11 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #153: Allow the use of MacPorts
In-Reply-To: <054.cf30bcc74b47ea1503f1ee4964c1ca23@nexusformat.org>
References: <054.cf30bcc74b47ea1503f1ee4964c1ca23@nexusformat.org>
Message-ID: <063.9c6393cb961ae498fe9ac253f590489c@nexusformat.org>

#153: Allow the use of MacPorts
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Stuart Campbell
      Type:  enhancement      |      Status:  closed         
  Priority:  major            |   Milestone:                 
 Component:  napi             |     Version:  trunk          
Resolution:  fixed            |    Keywords:                 
------------------------------+---------------------------------------------
Changes (by Stuart Campbell):

  * status:  assigned => closed
  * resolution:  => fixed

Comment:

 (In [1157]) fixes #153

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/153#comment:2>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 17:05:13 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 17:05:13 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.16b4c6a852fe61e4736c6346afac61e9@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Stuart Campbell):

 (In [1158]) refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:14>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 17:39:50 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 17:39:50 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #101: Python binding
In-Reply-To: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
References: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
Message-ID: <062.3ad852b8f823f579a9bcafb3eceb340a@nexusformat.org>

#101: Python binding
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Paul Kienzle   
      Type:  enhancement     |      Status:  reopened       
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  trunk          
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Paul Kienzle):

 (In [1159]) python: don't test i8 on hdf4. Refs #101.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/101#comment:23>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 18:19:23 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 18:19:23 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #154: Make x86_64 the default
 target on Mac OS X for the IDL bindings
Message-ID: <054.fe8427b97bb33ed6dad8f4b0fce58911@nexusformat.org>

#154: Make x86_64 the default target on Mac OS X for the IDL bindings
-----------------------------+----------------------------------------------
 Reporter:  Stuart Campbell  |       Owner:  Stuart Campbell
     Type:  task             |      Status:  new            
 Priority:  minor            |   Milestone:  NeXus 4.2 Ready
Component:  bindings         |     Version:  trunk          
 Keywords:                   |  
-----------------------------+----------------------------------------------


-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/154>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 18:19:49 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 18:19:49 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #154: Make x86_64 the default
 target on Mac OS X for the IDL bindings
In-Reply-To: <054.fe8427b97bb33ed6dad8f4b0fce58911@nexusformat.org>
References: <054.fe8427b97bb33ed6dad8f4b0fce58911@nexusformat.org>
Message-ID: <063.01860c5323e104be84d3aeb87cd3b7a2@nexusformat.org>

#154: Make x86_64 the default target on Mac OS X for the IDL bindings
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Stuart Campbell
      Type:  task             |      Status:  closed         
  Priority:  minor            |   Milestone:  NeXus 4.2 Ready
 Component:  bindings         |     Version:  trunk          
Resolution:  fixed            |    Keywords:                 
------------------------------+---------------------------------------------
Changes (by Stuart Campbell):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 (In [1160]) Make x86_64 the default for Mac OS X IDL bindings. fixes #154

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/154#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 18:22:09 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 18:22:09 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.d02b2132cdcfecdbc9205dd7d7e439f3@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Stuart Campbell):

 (In [1161]) Make x86_64 the default for Mac OS X IDL bindings. refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:15>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 21:24:10 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 21:24:10 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #144: IDL build problem
In-Reply-To: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
References: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
Message-ID: <062.8746d18c1c0a07ecc3b594c192c2b81a@nexusformat.org>

#144: IDL build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Stuart Campbell
      Type:  defect          |      Status:  reopened       
  Priority:  minor           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Changes (by Stuart Campbell):

  * status:  closed => reopened
  * resolution:  fixed =>

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/144#comment:5>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 21:24:45 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 21:24:45 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #144: IDL build problem
In-Reply-To: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
References: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
Message-ID: <062.e646cf35e7b1f6c7a9b67af8fff8c993@nexusformat.org>

#144: IDL build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Stuart Campbell
      Type:  defect          |      Status:  reopened       
  Priority:  minor           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Stuart Campbell):

 (In [1162]) Added check for 32bit CPU on Linux to return correct value for
 IDL directory. refs #144

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/144#comment:6>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 21:25:10 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 21:25:10 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #144: IDL build problem
In-Reply-To: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
References: <053.ab62c6882a647a68e76ba2dd9a74a52e@nexusformat.org>
Message-ID: <062.ebb327c9ecf45bd3974b8d150b412e99@nexusformat.org>

#144: IDL build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Stuart Campbell
      Type:  defect          |      Status:  closed         
  Priority:  minor           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  4.2rc2         
Resolution:  fixed           |    Keywords:                 
-----------------------------+----------------------------------------------
Changes (by Stuart Campbell):

  * status:  reopened => closed
  * resolution:  => fixed

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/144#comment:7>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 14 21:30:19 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 14 Jan 2009 21:30:19 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.e7ec37c17d33a719d352eb5d58561a19@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Stuart Campbell):

 (In [1163]) Added check for 32bit CPU on Linux to return correct value for
 IDL bin directory. refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:16>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Thu Jan 15 10:38:00 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Thu, 15 Jan 2009 10:38:00 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #152: Library for IDL bindings
	has the wrong name.
In-Reply-To: <054.cc566b61bb0d632b18dc1b5a69499d5d@nexusformat.org>
References: <054.cc566b61bb0d632b18dc1b5a69499d5d@nexusformat.org>
Message-ID: <063.149814a5d5aebfc5b616a4699e242a97@nexusformat.org>

#152: Library for IDL bindings has the wrong name.
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Unassigned     
      Type:  defect           |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  bindings         |     Version:  4.2rc2         
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1164]) Make local link to .so file. Refs #152.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/152#comment:2>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Thu Jan 15 10:40:38 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Thu, 15 Jan 2009 10:40:38 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #152: Library for IDL bindings
	has the wrong name.
In-Reply-To: <054.cc566b61bb0d632b18dc1b5a69499d5d@nexusformat.org>
References: <054.cc566b61bb0d632b18dc1b5a69499d5d@nexusformat.org>
Message-ID: <063.51917be60b6551e8aea6ae31674c1d31@nexusformat.org>

#152: Library for IDL bindings has the wrong name.
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Unassigned     
      Type:  defect           |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  bindings         |     Version:  4.2rc2         
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1165]) Make local link to .so file. Refs #152.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/152#comment:3>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Thu Jan 15 10:43:15 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Thu, 15 Jan 2009 10:43:15 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #101: Python binding
In-Reply-To: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
References: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
Message-ID: <062.63e379b2152391c09fa55d5224846abb@nexusformat.org>

#101: Python binding
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Paul Kienzle   
      Type:  enhancement     |      Status:  reopened       
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  trunk          
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1166]) python: don't test i8 on hdf4. Refs #101

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/101#comment:24>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Thu Jan 15 15:35:12 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Thu, 15 Jan 2009 15:35:12 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.f7f5ccfcb3daa40ea99dd8203606d7cf@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Mark Koennecke):

 (In [1167]) - Added test program for IDL, refs #151

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:3>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Thu Jan 15 19:12:28 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Thu, 15 Jan 2009 19:12:28 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.a651b1c882449d50c65d5a7ff227817d@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1168]) Add in automatic running of IDL test
 HDF5 test runs OK, HDF4 and XML fail
 Refs #151

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:4>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 16 12:31:31 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 16 Jan 2009 12:31:31 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #101: Python binding
In-Reply-To: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
References: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
Message-ID: <062.235c9a744b4813c77a7cad9611b82122@nexusformat.org>

#101: Python binding
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Paul Kienzle   
      Type:  enhancement     |      Status:  reopened       
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  trunk          
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1169]) Change directory when running python tests. Refs #101.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/101#comment:25>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 16 13:35:57 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 16 Jan 2009 13:35:57 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.433b260ba63c0fd5655730c7fdf0c1ec@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Paul Kienzle):

 hdf4 test now suppresses i8 test.

 xml/hdf4 are now failing because NXgroupinfo returns different results
 from HDF5 and HDF4/XML.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:3>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 16 13:40:53 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 16 Jan 2009 13:40:53 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #155: NXgroupinfo inconsistent
Message-ID: <051.64e790387df2ce56d8f334cfe37afe01@nexusformat.org>

#155: NXgroupinfo inconsistent
--------------------------+-------------------------------------------------
 Reporter:  Paul Kienzle  |       Owner:  Unassigned
     Type:  defect        |      Status:  new       
 Priority:  major         |   Milestone:            
Component:  napi          |     Version:  trunk     
 Keywords:                |  
--------------------------+-------------------------------------------------
 NXgroupinfo returns the group name for HDF4 and XML, but the group path
 for HDF5.  The documentation for NXgroupinfo says it should return the
 name.  There is no alternative mechanism for returning the path.

 Either change the docs, HDF4 and XML so that NXgroupinfo returns the path
 or create a new function NXgetpath which returns the path.

 The current python binding needs to know the path in order to support
 scanning through the entries in a group.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/155>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 16 14:11:36 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 16 Jan 2009 14:11:36 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.d08fd94d33fa6ec1b183afef8f135ed0@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1170]) Use == rather than "is" for comparison. Refs #149.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:4>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 16 23:26:19 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 16 Jan 2009 23:26:19 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.a49545d1b449c78b86969bb03071d2db@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Paul Kienzle):

 (In [1171]) xml getattrinfo now returns correct number of attrs for root;
 nxstest now skips bogus CDF0.0 entry in HDF4 root; nxs/napi.py now
 reimplements openpath so that nexus file knows its current path.  Refs
 #149.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:5>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Sat Jan 17 00:55:22 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Sat, 17 Jan 2009 00:55:22 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.d97386357a020facd1d89a7569b38184@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Paul Kienzle):

 (In [1172]) Improve handling of CDF0.0 and other HDF4 problems. Refs #149.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:6>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 19 12:16:18 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 19 Jan 2009 12:16:18 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.7b434fd1fad83037fd024421466b15ff@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  new              
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:                   |    Keywords:                   
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1173]) Adjust testsuite for fix to XML binding global attributes.
 Refs #149.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:7>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 19 17:30:32 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 19 Jan 2009 17:30:32 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #101: Python binding
In-Reply-To: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
References: <053.1d3384472f4febbf29eb7e182a3ff77f@nexusformat.org>
Message-ID: <062.d2ca219d63a845cd5d36266cf8b69944@nexusformat.org>

#101: Python binding
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Paul Kienzle   
      Type:  enhancement     |      Status:  reopened       
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  napi            |     Version:  trunk          
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1174]) MinGW fix for configure of python path. Refs #101.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/101#comment:26>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 19 17:51:56 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 19 Jan 2009 17:51:56 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.7e46d0e921224daf7a093352e3903653@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1175]) Fix XML global attributes for IDL test

 IDL test is still failing on  XML and HDF4
 * XML as print statement starts new line for long attributes (is there a
 way to force it not to start a new line with print in IDL?)
 * HDF4 with NXPUTDATA: ERROR: failure to write data to r4_data

 Refs #151

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:5>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 20 07:54:41 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 20 Jan 2009 07:54:41 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.cc2410257a50d96e050d6990dbe6ffb6@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Mark Koennecke):

 (In [1176]) - Imporved printing on long attributes though the
 specification of a
   format string to idl's print statement, refs #151

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:6>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 20 14:52:31 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 20 Jan 2009 14:52:31 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.743774086709a31e7c1bc32c39cd9f68@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1177]) Update test for [1176] - XML test now passes, but HDF4 still
 fails.
 Refs #151.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:7>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 21 12:28:57 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 21 Jan 2009 12:28:57 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.327469a71ac2483428b0f3749ad76348@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1178]) Update test to check XML characters are escaped correctly.
 Refs #115.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:17>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 21 16:41:44 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 21 Jan 2009 16:41:44 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.e7d5c6799402e90f808b5cac2d8e68c2@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1179]) Final fixes for IDL testsuite. Refs #151.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:8>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 21 16:46:34 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 21 Jan 2009 16:46:34 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.6a1cf5dd413aa57e48928d2822e3efbc@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1180]) Update 4.2 branch with trunk changes from r1163:r1179
 Refs #115

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:18>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 21 17:03:44 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 21 Jan 2009 17:03:44 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #151: IDL-API dumping core,
	Build problem
In-Reply-To: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
References: <053.62d47e369e27256db29d43ac19ab56d5@nexusformat.org>
Message-ID: <062.a3c8e0806a5bffe2f4c21793ff6b4c54@nexusformat.org>

#151: IDL-API dumping core, Build problem
-----------------------------+----------------------------------------------
  Reporter:  Mark Koennecke  |       Owner:  Mark Koennecke 
      Type:  defect          |      Status:  new            
  Priority:  major           |   Milestone:  NeXus 4.2 Ready
 Component:  bindings        |     Version:  4.2rc2         
Resolution:                  |    Keywords:                 
-----------------------------+----------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1181]) Remove --no-undefined as causes problem on MAC. It will be
 set in SHARED_LDFLAGS on MinGW. Refs #151.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/151#comment:9>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 21 17:05:22 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 21 Jan 2009 17:05:22 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #115: Create 4.2 branch and
	download kit
In-Reply-To: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
References: <054.f89034bccb9cb4c1b19f4ca83d096f5c@nexusformat.org>
Message-ID: <063.b189e856fb49109cec3171178d4b4686@nexusformat.org>

#115: Create 4.2 branch and download kit
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Freddie Akeroyd
      Type:  task             |      Status:  new            
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  napi             |     Version:  trunk          
Resolution:                   |    Keywords:                 
------------------------------+---------------------------------------------
Comment (by Freddie Akeroyd):

 (In [1182]) Update 4.2 branch with r1180:r1181 from trunk. Refs #115.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/115#comment:19>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 26 11:48:41 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 26 Jan 2009 11:48:41 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #156: python: support '|S1' for
	string data
Message-ID: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>

#156: python: support '|S1' for string data
------------------------------+---------------------------------------------
 Reporter:  Cpascual          |       Owner:  Unassigned
     Type:  defect            |      Status:  new       
 Priority:  minor             |   Milestone:            
Component:  bindings          |     Version:  4.2rc2    
 Keywords:  numpy dtype char  |  
------------------------------+---------------------------------------------
 It would be nice if '|S1' was accepted as a synonym of 'char' when passing
 dtype to napi functions.
 See attached patch to 4.2rc2 napi.py

 Rationale:
 Currently one can use numpy.dtype objects wherever a napi function
 requires dtype **except** for the case of string data.
 This is because the numpy-->nexus data type conversion is done through
 {{{
 _nxtype_code[str(type)]
 }}}

 In the case of numpy 1-character arrays, str(dtype) returns '|S1', so at
 least this case can be covered pretty easily by using the proposed patch.

 Note that this only works for numpy 1-character arrays, not for python
 strings. But at least one can convert to an array using:
 {{{
 numpy.array(tuple(string))
 }}}

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/156>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Mon Jan 26 12:24:17 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Mon, 26 Jan 2009 12:24:17 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #156: python: support '|S1'
	for string data
In-Reply-To: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
References: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
Message-ID: <056.4d6d1604d06bc32ce2f1d6c0998cf064@nexusformat.org>

#156: python: support '|S1' for string data
-----------------------+----------------------------------------------------
  Reporter:  Cpascual  |       Owner:  Paul Kienzle     
      Type:  defect    |      Status:  new              
  Priority:  minor     |   Milestone:  NeXus 4.2 Release
 Component:  bindings  |     Version:  4.2rc2           
Resolution:            |    Keywords:  numpy dtype char 
-----------------------+----------------------------------------------------
Changes (by Freddie Akeroyd):

  * owner:  Unassigned => Paul Kienzle
  * milestone:  => NeXus 4.2 Release

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/156#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Tue Jan 27 09:42:45 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Tue, 27 Jan 2009 09:42:45 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #156: python: support '|S1'
	for string data
In-Reply-To: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
References: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
Message-ID: <056.dfd45518d3d94e321d3db14b750605f9@nexusformat.org>

#156: python: support '|S1' for string data
-----------------------+----------------------------------------------------
  Reporter:  Cpascual  |       Owner:  Paul Kienzle     
      Type:  defect    |      Status:  new              
  Priority:  minor     |   Milestone:  NeXus 4.2 Release
 Component:  bindings  |     Version:  4.2rc2           
Resolution:            |    Keywords:  numpy dtype char 
-----------------------+----------------------------------------------------
Comment (by Cpascual):

 On a deeper test, I see that my patch is not sufficient... some other
 functions such as {{{_pinput}}} do comparisons looking for "char" but then
 {{{_is_string_like()}}} evaluates to False when using numpy arrays of
 characters...

 Still it would be nice if we could somehow get rid of the inconsistent
 handling of "char" VS the other datatypes that are numpy.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/156#comment:2>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Wed Jan 28 15:42:14 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Wed, 28 Jan 2009 15:42:14 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #157: Possible problem in python
	openpath()
Message-ID: <054.56775890e4c1068824aaf0b93fa83192@nexusformat.org>

#157: Possible problem in python openpath()
-----------------------------+----------------------------------------------
 Reporter:  Stuart Campbell  |       Owner:  Paul Kienzle   
     Type:  defect           |      Status:  new            
 Priority:  major            |   Milestone:  NeXus 4.2 Ready
Component:  bindings         |     Version:  trunk          
 Keywords:  python           |  
-----------------------------+----------------------------------------------
 I was just looking at the openpath routine in the python bindings and I
 noticed the use of the {{{NXgetgroupinfo}}} function to return the number
 of child elements (line 493).[[BR]]

 I thought that this function returned the number of attributes rather than
 the number of elements.

 This might not be a problem, but I thought it was worth pointing it out.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/157>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 30 14:22:56 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 30 Jan 2009 14:22:56 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #157: Possible problem in
	python openpath()
In-Reply-To: <054.56775890e4c1068824aaf0b93fa83192@nexusformat.org>
References: <054.56775890e4c1068824aaf0b93fa83192@nexusformat.org>
Message-ID: <063.071b314c87f86b3002580a9d2b801ced@nexusformat.org>

#157: Possible problem in python openpath()
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Paul Kienzle   
      Type:  defect           |      Status:  closed         
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  bindings         |     Version:  trunk          
Resolution:  invalid          |    Keywords:  python         
------------------------------+---------------------------------------------
Changes (by Paul Kienzle):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 The docs say that getgroupinfo returns number of elements and getattrinfo
 returns the number of attributes.  This is how it works in practice as
 well, otherwise NXinstrument would never be able to load.

 I will close this ticket until someone can demonstrate failure.

 Note: HDF4 files can have a bogus group at the root level that is not part
 of the nexus file.  The entries iterator suppresses it.  Since the doc
 string on NeXus.entries for more details.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/157#comment:1>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 30 14:27:00 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 30 Jan 2009 14:27:00 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #149: python test script fails
	with hdf4 and xml
In-Reply-To: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
References: <054.28f8d61e3f91c61b701ffb62f11e11c6@nexusformat.org>
Message-ID: <063.81fb6360ae3dd518238621b56f2ba7b8@nexusformat.org>

#149: python test script fails with hdf4 and xml
------------------------------+---------------------------------------------
  Reporter:  Freddie Akeroyd  |       Owner:  Paul Kienzle     
      Type:  defect           |      Status:  closed           
  Priority:  major            |   Milestone:  NeXus 4.2 Release
 Component:  napi             |     Version:  4.2rc2           
Resolution:  fixed            |    Keywords:                   
------------------------------+---------------------------------------------
Changes (by Paul Kienzle):

  * status:  new => closed
  * resolution:  => fixed

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/149#comment:8>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 30 14:46:50 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 30 Jan 2009 14:46:50 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #156: python: support '|S1'
	for string data
In-Reply-To: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
References: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
Message-ID: <056.01271c415b1a862840a46ee603754e6c@nexusformat.org>

#156: python: support '|S1' for string data
-----------------------+----------------------------------------------------
  Reporter:  Cpascual  |       Owner:  Paul Kienzle     
      Type:  defect    |      Status:  new              
  Priority:  minor     |   Milestone:  NeXus 4.2 Release
 Component:  bindings  |     Version:  4.2rc2           
Resolution:            |    Keywords:  numpy dtype char 
-----------------------+----------------------------------------------------
Comment (by Paul Kienzle):

 Before trying to fix this, I would like to understand why you are passing
 numpy character arrays instead of python strings.

 Getting the interface to act consistently so that you get the same value
 back on read that you put in on write could be tricky.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/156#comment:3>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 30 15:50:09 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 30 Jan 2009 15:50:09 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #156: python: support '|S1'
	for string data
In-Reply-To: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
References: <047.f55ad3f5026d39845c77f96d333b3f33@nexusformat.org>
Message-ID: <056.821d310ee4a05494d34105858ec51991@nexusformat.org>

#156: python: support '|S1' for string data
-----------------------+----------------------------------------------------
  Reporter:  Cpascual  |       Owner:  Paul Kienzle     
      Type:  defect    |      Status:  new              
  Priority:  minor     |   Milestone:  NeXus 4.2 Release
 Component:  bindings  |     Version:  4.2rc2           
Resolution:            |    Keywords:  numpy dtype char 
-----------------------+----------------------------------------------------
Comment (by Cpascual):

 The ability to deal with numpy string arrays as the **input** would be
 interesting for two reasons:

 1) It makes the API more consistent (one would not need act differently
 depending on whether is using 'char' or other types)

 2)It paves the path to multidimensional character arrays.



 Regarding the **output**: IMHO, the output should be always the same
 regardless of the input, and only dependent on the data shape (i.e., on
 what is returned by NXgetinfo(). I think that the most consistent option
 is to always return a numpy array of strings:

 If the data shape is [m], then the output should be a zero-dimensional
 numpy array containing a string of length m

 If the data shape is [n,m], then the output should be a n-long 1D numpy
 array of strings of length m.

 If the data shape is [k,n,m] then the output should be a 2D array [with
 shape=(k,n)] of strings of length m.

 ...

 As an exception it could be reasonable to implement it in such a way that
 data with shape [m] returns a python string instead of a numpy array of
 shape=(,). But, IMHO, always returning numpy makes it more self-
 consistent. The user can always convert the output (or slices of it) to
 strings using the .tostring() method of the numpy arrays.

 I am currently working on my own implementation of this. I will post it as
 soon as it is ready.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/156#comment:4>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 30 15:58:05 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 30 Jan 2009 15:58:05 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #157: Possible problem in
	python openpath()
In-Reply-To: <054.56775890e4c1068824aaf0b93fa83192@nexusformat.org>
References: <054.56775890e4c1068824aaf0b93fa83192@nexusformat.org>
Message-ID: <063.8558ef508b1def05589b0e573300064f@nexusformat.org>

#157: Possible problem in python openpath()
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Paul Kienzle   
      Type:  defect           |      Status:  reopened       
  Priority:  major            |   Milestone:  NeXus 4.2 Ready
 Component:  bindings         |     Version:  trunk          
Resolution:                   |    Keywords:  python         
------------------------------+---------------------------------------------
Changes (by Peter Peterson):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 The documentation in [source:trunk/include/napi.h at 1042 napi.h] disagrees
 with you. Quoting that directly lines 501-511.
 {{{
   /**
    * Retrieve information about the currently open group.
    * \param handle A NeXus file handle as initialized by NXopen.
    * \param no_items A pointer to an integer which will be set to the
 count of group attributes
    * available.
    * \param name The name of the group.
    * \param nxclass The NeXus class name of the group.
    * \return NX_OK on success, NX_ERROR in the case of an error.
    */
 extern  NXstatus  NXgetgroupinfo(NXhandle handle, int* no_items, NXname
 name, NXname nxclass);
 }}}
 The integer is the number of attributes on the group. {{{NXgetattrinfo}}}
 returns the number of attributes for the current field. I don't believe it
 returns any information for group attributes.

 To get all of the groups/fields at the current level you should use
 {{{NXgetnextentry}}} until {{{NX_EOD}}} is returned.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/157#comment:2>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


From noreply at nexusformat.org  Fri Jan 30 23:49:30 2009
From: noreply at nexusformat.org (NeXus Data Format Library and Applications)
Date: Fri, 30 Jan 2009 23:49:30 -0000
Subject: [NeXus-code-tickets] [NeXusCode] #157: Possible problem in
	napi.h documentation
In-Reply-To: <054.56775890e4c1068824aaf0b93fa83192@nexusformat.org>
References: <054.56775890e4c1068824aaf0b93fa83192@nexusformat.org>
Message-ID: <063.069dcf35df6c33ef6215e2c36ce585af@nexusformat.org>

#157: Possible problem in napi.h documentation
------------------------------+---------------------------------------------
  Reporter:  Stuart Campbell  |       Owner:  Paul Kienzle   
      Type:  defect           |      Status:  reopened       
  Priority:  minor            |   Milestone:  NeXus 4.2 Ready
 Component:  documentation    |     Version:  trunk          
Resolution:                   |    Keywords:  getgroupinfo   
------------------------------+---------------------------------------------
Changes (by Paul Kienzle):

  * keywords:  python => getgroupinfo
  * priority:  major => minor
  * component:  bindings => documentation
  * summary:  Possible problem in python openpath() => Possible problem in
              napi.h documentation

Comment:

 http://www.nexusformat.org/NAPI_Routines#NXgetgroupinfo

 Quoting:

     NXgetgroupinfo
     Returns the number of items in the current group, and the name and
 class of the current group.
     ...
     Output Arguments
       item_number        int *   Number of NeXus data items in the current
 group
       group_name         char *  Name of currently open NeXus group
       group_class        char *  Class of currently open NeXus group

 Looking in the source:

    HDF4: Vntagrefs returns the number of objects in a vgroup identified by
 the parameter vgroup_id.
    HDF5: iteratate over groups with group_info1: increments iNX if type is
 H5G_GROUP or H5G_DATASET
    XML: loop over child incrementing childCount

 And more importantly my code would fail if the getgroupinfo were returning
 the wrong thing.

 I'll leave this open until the doc issues are resolved, and rename it to a
 napi.h problem.

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/157#comment:3>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications


