-
Currently, the indices to get grains out of `hrdic.Map` are off by one relative to the integer IDs in the `hrdic.Map.grains` image. That is, `hrdic.Map[0]` gets the grain that has value 1 in the image…
-
Issues to fix for davis 10 format
- [ ] Coordinate values are formatted as floats (even for int values)
- [ ] Coordinate values are not necessarily integers (Only half integers because of odd size…
-
How difficult would it be to link the the raw image to the grain segmented via EBSD? For example, we might like to see how the slip interacts with features in the raw image (particles, second phases e…
-
The process of matching grains in a DIC to EBSD map needs to be made more robust or some error handling added so the process does not completely fail if match is not found. A typical error that can oc…
-
I wrote a bit of code a while ago, to deal with DIC data from multiple deformation steps.
The way I implemented it was to have a different class (called Maps as opposed to Map), that you initialise…
-
An error has emerged in the findGrains function in the latest release of defdap.
Even though nothing has changed in the code, the following error occurs in the docs (which were recently recompiled)…
-
I gather I can load either cpr+crc file or a ctf file from Oxford / Aztec. It looks like there is also an option for a python-based database.
What are people regularly doing to load EDAX type data? (…
-
Memory usage of DefDAP can be quite high. For two EBSD maps (admittedly quite large ones) - it occupies ~1.4 GB of memory. For two large HRDIC maps, it's using ~1.8 GB. This makes it tricky to compare…
-
-
Hi all,
My colleague and I are working on some analysis of HRDIC data with the use of the Grain Inspector interface. We are using the develop branch and everything is working fine for me in Mac. Ho…