How to resolve hdf5 conflicts in User Files and in a Macro

Share icon

Fri, 07/28/2017 - 07:46 am

I have a question regarding the hdf5 extension and User Files path.

I have multiple copies of IGOR currently - each within a separate folder so they can have different Igor Pro Folders. I've had to do it this way as they are for different pieces of software/ have different extensions and macros for different experiments that would otherwise conflict (I tried having them all in the same instance and it didn't compile).

One of these copies has a macro incorporated that runs the hdf5 browser (I didn't write this package so its pretty much a black box to me) but it works fine and opens/ writes hdf5 files as expected.

I would like to install the hdf5 Browser for my other copies of Igor so I followed the installation instructions on putting the correct shortcuts in the Igor Pro Use Files folders. this resulted in it working fine for my other copies, but for the version that already had this hdf5 within a macro, it would no longer compile or open as normal, so didn't work anymore, as it now had multiple conflicting hdf5 packages.

My question is: is there a way to have separate Igor Pro User Files for these different copies of Igor? I've changed location in Misc. settings to a different folder but this changes the path for all my copies so doesn't solve the problem.

I've tried to explain as best I can but please let me know if more information would be helpful

Thanks for any help!
Have you tried to separate your procedure files into "User Procedures" and "Igor Procedures". The former can be loaded on demand, while the latter are always loaded.

I'm not sure I understand the conflict issue though.

July 28, 2017 at 08:56 am - Permalink

I suspect that you have the "HDF5 Browser.ipf" procedures copied into your own procedure file. When you activated "HDF5 Browser.ipf" via the "Igor Procedures" folder, this causes Igor to automatically open the file. Now you have two copies of the same procedure, so you get compile errors.

The correct solution is to remove the copy from your own procedures and to rely only on the activated "HDF5 Browser.ipf" file.

July 29, 2017 at 05:24 am - Permalink