New version 2.71

The “Coco Bongo” release.
Speed up of the spherical component calculation in standard functions in the case of texture broadening coefficients. Corrected the behaviour of the omega offset in the Hippo Wizard.

6 Comments on “New version 2.71

  1. Hi Luca,

    the new versions don’t respond to


    in parameters and always save the spectra with the PAR file. That prevents me from re-using an analysis on a different data set. With the script below users may strip the data out, replace file names and re-load a PAR file to re-cycle an analysis:

    awk ‘{
    if(NR == 1){output=”on”}
    if($0 ~ /\#custom_object_intensity_data/){output=”off”; next}
    if($0 ~ /\#end_custom_object_intensity_data/){output=”on”; next}
    if(output == “on”){print}
    }’ $1

    maybe can be fixed in the next release?

  2. Hi Luca, I had to use the absorption model for neutron TOF quite extensively and I believe the assumption that you can model a sample geometry for all histograms is incorrect: Since the only variable parameters in the absorption model in MAUD are a sample length for a given sample direction, we are ignoring the fact that the same sample direction can be measured with two detectors, let’s say 40 and 144 on HIPPO. For a cylinder, the 144s would see the direction in reflection, the 40s would see it transmission geometry. Both have very different travel path in the sample that cannot be modeled with a single sample geometry.

    If I am not misunderstanding the MAUD model, I propose that we need a different absorption model. I suggest the one implemented in GSAS, with one absorption parameter per histogram, independent of the sample direction.

  3. Another wish for the upcoming Iguana Release:

    The interpolated background is great, but right now I have to either accept what the algorithm comes up with for the location of the points or manually edit 135 histograms…

    Is it possible to create a position list in d-spacing for all detectors? Assuming that all detectors see the same phases, besides peak width the patterns and therefore the interpolation points will be similar. I could then manually fine tune a worst resolution pattern and then somehow link all other patterns to that master pattern, no matter what detector band I am working with.

    This would be really useful!

  4. I tried to look into the preferences file and it took me a while to find it. On my Linux system I can see it with

    [sven@svenslaptop maud]$ cat ~/.java/.userPrefs/_\!\’k\!d\!\!u\!\(\`\!bg\”p\!\(@\!bg\!u\!\’k\!bg\”n\!#4\!cg\”p\!\(\:\!d\!\”h\!#4\!d@\”0\!\’k\!b\!\!u\!%0\!\}@\”1\!\’@\!\`\!\”y\!\’\`\!~g\”l\!\(\)\!~@\”u\!\’\:\!~@\”z/prefs.xml

    Is there an easier path one could use? I am having no luck in changing the default path to load an analysis from ../maud/doc to my folder. If I change it in preferences, I see that the above file us updated, but it goes back to the doc folder. If I change it in the prefs.xml file in an editor and open Maud, it also goes back to the doc folder, even if I just delete the maud/doc/ part to make sure I have a valid folder.

    Seems like the new preferences system is still buggy?

  5. When I downloaded the latest version and open Maud.bat. There is something wrong with it on the console window shown as below.

    Lib dir: lib
    Check paths and libraries….
    Reading from jar file: lib\Maud.jar, entry(files/atominfo.cif)
    Reading from jar file: lib\Maud.jar, entry(files/CWWARRAY.DAT)
    Reading from jar file: lib\Maud.jar, entry(files/IADARRAY.DAT)
    cctbx native library not loaded, using SgInfo!
    java.lang.UnsatisfiedLinkError: no cctbxForMaud in java.library.path
    at java.lang.ClassLoader.loadLibrary(
    at java.lang.Runtime.loadLibrary0(
    at java.lang.System.loadLibrary(
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(
    at com.radiographema.Maud.programInitialization(
    at com.radiographema.Maud.initInteractive(
    at com.radiographema.Maud.main(

    • It’s normal, don’t worry. Maud will work one day with the cctbx library instead of the built in SgInfo for all crystallographic computations.
      But the cctbxForMaud interface is still under testing and not included in the distributed official Maud version. So you see the error. When the cctbx layer will be ready and included, the error will disappear.


Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.