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
Disarmed scanner: 12-Oct-2022 09:05:26
resetting abort flags
Tearing down scanner
Requested 352 slices: this is 17.60 mm thick but only 1.50 mm is possible. Setting to the maximum value of 28 slices.
BAKE FAILED IN acquisition_view. CAUGHT THE FOLLOWING ERROR:
Reference to non-existent field 'BoundingBoxDetails'.
Line 74 in C:\MATLAB\BakingTray\code\@BT\populateCurrentTilePattern.m
Line 162 in C:\MATLAB\BakingTray\code\@BT\getNextROIs.m
Line 342 in C:\MATLAB\BakingTray\code\@BT\bake.m
Line 68 in C:\MATLAB\BakingTray\code\+BakingTray\+gui\@acquisition_view\bake_callback.m
Line 61 in C:\MATLAB\BakingTray\code\+BakingTray\+gui\@acquisition_view\buildFigure.m
Reference to non-existent field 'BoundingBoxDetails'.
Error in BT/populateCurrentTilePattern (line 74)
BB = obj.autoROI.stats.roiStats(end).BoundingBoxDetails;
Error in BT/getNextROIs (line 162)
obj.populateCurrentTilePattern
Error in BT/bake (line 342)
success = obj.getNextROIs;
Error in BakingTray.gui.acquisition_view/bake_callback (line 68)
sectionInd = obj.model.bake; %if the bake loop didn't start, it returns 0
Error in BakingTray.gui.acquisition_view/buildFigure>@(varargin)obj.bake_callback(varargin{:}) (line 61)
'Callback', @obj.bake_callback, ...
Error while evaluating UIControl Callback.
The sample was imaged completely in autoROI mode. It, however, seemed to be imaging the agar block and by the end there is zero tissue left. No idea what caused the error.
EDIT: woah! NV and BS both produced this new error message for the first time at the same time.
The text was updated successfully, but these errors were encountered:
The sample was imaged completely in autoROI mode. It, however, seemed to be imaging the agar block and by the end there is zero tissue left. No idea what caused the error.
EDIT: woah! NV and BS both produced this new error message for the first time at the same time.
The text was updated successfully, but these errors were encountered: