Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export levels below 3 tend to fail #11

Open
jab0707 opened this issue Jan 23, 2024 · 0 comments
Open

Export levels below 3 tend to fail #11

jab0707 opened this issue Jan 23, 2024 · 0 comments

Comments

@jab0707
Copy link
Contributor

jab0707 commented Jan 23, 2024

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

vtkWrite(o.m1Ventricles.debug, sprintf('%so.m1VentriclesFinalAb.vtu', o.cfg.outPrefix));

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant