You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 initialised by giving a path and file names to the DIC data. You can then do things like link an EBSD map, or set homog points, scales, crops etc for all the DIC maps in one go. The key thing I used it for was plotting a DIC map with a slider at the bottom to flip between steps. Additionally, I also made it so that you can call Maps[1] to give the corresponding Map.
It will need some improvement before adding into the repo though, but wanted to see if this would be useful for anyone.
The text was updated successfully, but these errors were encountered:
This sounds good but I think the structure could be a little more generic. Perhaps have an "experiment" container class which contains multiple "timesteps". Each time step could then contain the data (DIC/EBSD/maybe images eventually) collected at that point. The HRDIC maps could then reference that they are expressed in the coordinates of the first time step and it would know to use homologous points defined in that step. Just some ideas, happy to discuss what you have already!
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 initialised by giving a path and file names to the DIC data. You can then do things like link an EBSD map, or set homog points, scales, crops etc for all the DIC maps in one go. The key thing I used it for was plotting a DIC map with a slider at the bottom to flip between steps. Additionally, I also made it so that you can call Maps[1] to give the corresponding Map.
It will need some improvement before adding into the repo though, but wanted to see if this would be useful for anyone.
The text was updated successfully, but these errors were encountered: