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
There are a few places throughout the code that write out debug outputs which, if the export level is set to 1, are not actually set and therefore fail. One example is in computeApicobasalVentricles.m Here it writes out a debug output of the apicobasal coordinate using
However, if export level is set to 1 this will fail because 0.m1Ventricles.debug will have no points or cells. This is because in preparemesh1.m o.m1.debug is set to be the o.m1.vol only if export level >1:
if o.cfg.exportLevel > 1
o.m1.debug = o.m1.vol;
o.m1.debug.pointData.surClass = repmat(uint8(0),size(o.m1.debug.points,1),1);
o.m1.debug.pointData.surClass(o.m1.surToVol) = o.m1.sur.pointData.class;
end
There are a few other spots around the code that do something similar, and even at export level 1, many many extra files are written that are not needed.
The text was updated successfully, but these errors were encountered:
There are a few places throughout the code that write out debug outputs which, if the export level is set to 1, are not actually set and therefore fail. One example is in computeApicobasalVentricles.m Here it writes out a debug output of the apicobasal coordinate using
However, if export level is set to 1 this will fail because 0.m1Ventricles.debug will have no points or cells. This is because in preparemesh1.m o.m1.debug is set to be the o.m1.vol only if export level >1:
There are a few other spots around the code that do something similar, and even at export level 1, many many extra files are written that are not needed.
The text was updated successfully, but these errors were encountered: