I have two vector(which are time stamps) like,

V N

1375471092848936 1375473384440853
1375473388165900 1375471277856598
1375471320476780 1375473388165900
1375473388947681 1375471322465961
1375473392527002 1375471335206288
……………… ………………

My goal is to find closest time in N with respect to V (i.e. find time in N which is nearly equal with V). My frame is W = 1e4, furthermore V should lies between N-W and N+W. So how do I get closest time through MATLAB? Any help would be appreciated.

ThanksI have two vector(which are time stamps) like,

V N

1375471092848936 1375473384440853
1375473388165900 1375471277856598
1375471320476780 1375473388165900
1375473388947681 1375471322465961
1375473392527002 1375471335206288
……………… ………………

My goal is to find closest time in N with respect to V (i.e. find time in N which is nearly equal with V). My frame is W = 1e4, furthermore V should lies between N-W and N+W. So how do I get closest time through MATLAB? Any help would be appreciated.

Thanks I have two vector(which are time stamps) like,

V N

1375471092848936 1375473384440853
1375473388165900 1375471277856598
1375471320476780 1375473388165900
1375473388947681 1375471322465961
1375473392527002 1375471335206288
……………… ………………

My goal is to find closest time in N with respect to V (i.e. find time in N which is nearly equal with V). My frame is W = 1e4, furthermore V should lies between N-W and N+W. So how do I get closest time through MATLAB? Any help would be appreciated.

Thanks vector, array, closest value MATLAB Answers — New Questions

​

Hello everyone,
i´m having a Simulink Model which consists of custom library blocks. The connections between the blocks can be seen in the attached picture (BlockDiagramm.jpg ; highlighted trace).
During connecting the blocks, the Matlab Command Window gets filled with a lot of warning messages from same type:
"Warning: Trace to source might be incomplete because the trace enters a loop at output port 1 of …"
When I run the model, no warning or error message appears (-> Simulink is able to solve it and serves correct values).
So i´m wondering about the behaviour during building the model – why does Matlab send those warning messages before running the model and how to get rid of them? For signals in a loop I use the "Unit Delay"-Block.

Typing >> Simulink.BlockDiagram.getAlgebraicLoops(bdroot) << provides:
No algebraic loops were found.
ans =
0×0 AlgebraicLoop array with properties:
Model
Id
VariableBlockHandles
BlockHandles
IsArtificial
Typing >> w = warning(‘query’,’last’) << provides:
identifier: ‘Simulink:HiliteTool:LineTracingBusLoopWarning’
state: ‘on’

I know that i can turn the warning off using warning(‘off’,w.identifier) – but it would be nice to debug my model. And if there is not a problem with the model in general, I´d like to disable this warning constantly. It has to be said, that the warning does not appear on the diagnostic screen in Simulink, but in the Command Window in Matlab. Turning off "Edit-Time Errors and Warnings" in Simulink doesn´t help.
Thanks for your answers in advance.Hello everyone,
i´m having a Simulink Model which consists of custom library blocks. The connections between the blocks can be seen in the attached picture (BlockDiagramm.jpg ; highlighted trace).
During connecting the blocks, the Matlab Command Window gets filled with a lot of warning messages from same type:
"Warning: Trace to source might be incomplete because the trace enters a loop at output port 1 of …"
When I run the model, no warning or error message appears (-> Simulink is able to solve it and serves correct values).
So i´m wondering about the behaviour during building the model – why does Matlab send those warning messages before running the model and how to get rid of them? For signals in a loop I use the "Unit Delay"-Block.

Typing >> Simulink.BlockDiagram.getAlgebraicLoops(bdroot) << provides:
No algebraic loops were found.
ans =
0×0 AlgebraicLoop array with properties:
Model
Id
VariableBlockHandles
BlockHandles
IsArtificial
Typing >> w = warning(‘query’,’last’) << provides:
identifier: ‘Simulink:HiliteTool:LineTracingBusLoopWarning’
state: ‘on’

I know that i can turn the warning off using warning(‘off’,w.identifier) – but it would be nice to debug my model. And if there is not a problem with the model in general, I´d like to disable this warning constantly. It has to be said, that the warning does not appear on the diagnostic screen in Simulink, but in the Command Window in Matlab. Turning off "Edit-Time Errors and Warnings" in Simulink doesn´t help.
Thanks for your answers in advance. Hello everyone,
i´m having a Simulink Model which consists of custom library blocks. The connections between the blocks can be seen in the attached picture (BlockDiagramm.jpg ; highlighted trace).
During connecting the blocks, the Matlab Command Window gets filled with a lot of warning messages from same type:
"Warning: Trace to source might be incomplete because the trace enters a loop at output port 1 of …"
When I run the model, no warning or error message appears (-> Simulink is able to solve it and serves correct values).
So i´m wondering about the behaviour during building the model – why does Matlab send those warning messages before running the model and how to get rid of them? For signals in a loop I use the "Unit Delay"-Block.

Typing >> Simulink.BlockDiagram.getAlgebraicLoops(bdroot) << provides:
No algebraic loops were found.
ans =
0×0 AlgebraicLoop array with properties:
Model
Id
VariableBlockHandles
BlockHandles
IsArtificial
Typing >> w = warning(‘query’,’last’) << provides:
identifier: ‘Simulink:HiliteTool:LineTracingBusLoopWarning’
state: ‘on’

I know that i can turn the warning off using warning(‘off’,w.identifier) – but it would be nice to debug my model. And if there is not a problem with the model in general, I´d like to disable this warning constantly. It has to be said, that the warning does not appear on the diagnostic screen in Simulink, but in the Command Window in Matlab. Turning off "Edit-Time Errors and Warnings" in Simulink doesn´t help.
Thanks for your answers in advance. warning linetracing, busloop MATLAB Answers — New Questions

​

Has anyone else had issues with the functionality of ginput with app designer created figures? On seemingly random occasions when ginput is called, the "mouse" pointer predictabily dissappears, but the crosshairs do not appear, leaving the user blind as to where they are on the figure. When this occurs, there appears to be no way to correct it other than to restart the application and losing all progress. The inputs DO still register when the user clicks on the figure though! There are also no errors when the callback is run and the line function run after with these inputs (shown below) will plot on the axes.
I have tried setting the handle visibility to ‘callback’ and specifying the current figure to try to "point" the function to the app figure, but this hasn’t prevented the issue.
For additional context, what I am doing is receiving user input of a range of X values on a 1D plot or 2D matrix, plotted on an app.UIAxes, and store the info in a cell array. The user must cycle through multiple plots/matrices and the app updates the values as they are changed. "r" is the index of the plot they are on, and "e" is the index of the selected input range. The user can add multiple "e"s (input ranges) through an add tool which also utilizes the ginput function.
I have used ginput in a number of ways to collect input on matrices/images as well, and frequently encounter this issue. I’m aware there is a separate selection tool on the axes object however I don’t know how to use it accordingly to programmatically recieve the values in a callback.

function EditPointsButtonPushed(app, event)
r = app.r;
e = app.e
assert(~verLessThan(‘Matlab’, ‘9.9’), ‘ginput not supported prior to Matlab r2020b.’)
fhv = app.UIFigure.HandleVisibility
app.UIFigure.HandleVisibility = ‘callback’
set(0, ‘CurrentFigure’, app.UIFigure)
[X1 ~] = ginput(2)
app.UIFigure.HandleVisibility = fhv;
line([X1(1) X1(1)],[Ymin max(app.Eventplots{r,e}(:,2))]); %1 needs to be axis min
line([X1(2) X1(2)],[Ymin max(app.Eventplots{r,e}(:,2))]);
app.Editpoints = round(X1)
end

I should also mention that the app is structured with a gridlayout, with panels that contain the axes. I thought that possibly ginput was occasionally being called onto the figure underneath these panels, however as others have mentioned in other questions, you cannot specify ginput onto objects/axes/etc and I cannot see the cursor when I move it between panels. I’m not sure what else to try, so any ideas would be greatly appreciated!!Has anyone else had issues with the functionality of ginput with app designer created figures? On seemingly random occasions when ginput is called, the "mouse" pointer predictabily dissappears, but the crosshairs do not appear, leaving the user blind as to where they are on the figure. When this occurs, there appears to be no way to correct it other than to restart the application and losing all progress. The inputs DO still register when the user clicks on the figure though! There are also no errors when the callback is run and the line function run after with these inputs (shown below) will plot on the axes.
I have tried setting the handle visibility to ‘callback’ and specifying the current figure to try to "point" the function to the app figure, but this hasn’t prevented the issue.
For additional context, what I am doing is receiving user input of a range of X values on a 1D plot or 2D matrix, plotted on an app.UIAxes, and store the info in a cell array. The user must cycle through multiple plots/matrices and the app updates the values as they are changed. "r" is the index of the plot they are on, and "e" is the index of the selected input range. The user can add multiple "e"s (input ranges) through an add tool which also utilizes the ginput function.
I have used ginput in a number of ways to collect input on matrices/images as well, and frequently encounter this issue. I’m aware there is a separate selection tool on the axes object however I don’t know how to use it accordingly to programmatically recieve the values in a callback.

function EditPointsButtonPushed(app, event)
r = app.r;
e = app.e
assert(~verLessThan(‘Matlab’, ‘9.9’), ‘ginput not supported prior to Matlab r2020b.’)
fhv = app.UIFigure.HandleVisibility
app.UIFigure.HandleVisibility = ‘callback’
set(0, ‘CurrentFigure’, app.UIFigure)
[X1 ~] = ginput(2)
app.UIFigure.HandleVisibility = fhv;
line([X1(1) X1(1)],[Ymin max(app.Eventplots{r,e}(:,2))]); %1 needs to be axis min
line([X1(2) X1(2)],[Ymin max(app.Eventplots{r,e}(:,2))]);
app.Editpoints = round(X1)
end

I should also mention that the app is structured with a gridlayout, with panels that contain the axes. I thought that possibly ginput was occasionally being called onto the figure underneath these panels, however as others have mentioned in other questions, you cannot specify ginput onto objects/axes/etc and I cannot see the cursor when I move it between panels. I’m not sure what else to try, so any ideas would be greatly appreciated!! Has anyone else had issues with the functionality of ginput with app designer created figures? On seemingly random occasions when ginput is called, the "mouse" pointer predictabily dissappears, but the crosshairs do not appear, leaving the user blind as to where they are on the figure. When this occurs, there appears to be no way to correct it other than to restart the application and losing all progress. The inputs DO still register when the user clicks on the figure though! There are also no errors when the callback is run and the line function run after with these inputs (shown below) will plot on the axes.
I have tried setting the handle visibility to ‘callback’ and specifying the current figure to try to "point" the function to the app figure, but this hasn’t prevented the issue.
For additional context, what I am doing is receiving user input of a range of X values on a 1D plot or 2D matrix, plotted on an app.UIAxes, and store the info in a cell array. The user must cycle through multiple plots/matrices and the app updates the values as they are changed. "r" is the index of the plot they are on, and "e" is the index of the selected input range. The user can add multiple "e"s (input ranges) through an add tool which also utilizes the ginput function.
I have used ginput in a number of ways to collect input on matrices/images as well, and frequently encounter this issue. I’m aware there is a separate selection tool on the axes object however I don’t know how to use it accordingly to programmatically recieve the values in a callback.

function EditPointsButtonPushed(app, event)
r = app.r;
e = app.e
assert(~verLessThan(‘Matlab’, ‘9.9’), ‘ginput not supported prior to Matlab r2020b.’)
fhv = app.UIFigure.HandleVisibility
app.UIFigure.HandleVisibility = ‘callback’
set(0, ‘CurrentFigure’, app.UIFigure)
[X1 ~] = ginput(2)
app.UIFigure.HandleVisibility = fhv;
line([X1(1) X1(1)],[Ymin max(app.Eventplots{r,e}(:,2))]); %1 needs to be axis min
line([X1(2) X1(2)],[Ymin max(app.Eventplots{r,e}(:,2))]);
app.Editpoints = round(X1)
end

I should also mention that the app is structured with a gridlayout, with panels that contain the axes. I thought that possibly ginput was occasionally being called onto the figure underneath these panels, however as others have mentioned in other questions, you cannot specify ginput onto objects/axes/etc and I cannot see the cursor when I move it between panels. I’m not sure what else to try, so any ideas would be greatly appreciated!! ginput, app designer, uifigure, pointer, plot MATLAB Answers — New Questions

​

I have a MATLAB 2022 code that used the poly.intersect function–I can’t find in R2024 and need a workaround to compute the intersection of polygons. The code is below. In line 12 the polyIntersect function is used:
[OutData(ii).intsecArea(i).Data, S] = polyIntersect(CoRegErrData, inPolyNewsub, inPolyOldsub);
How do I modify the code in lieu of using polyIntersect ?
for ii = 1:length(hucPoly)
hucSub = polyshape(hucPoly(ii).X, hucPoly(ii).Y);
hucID = hucPoly(ii).Name;
OutData(ii).hucID = hucID;
for i = 1:size(inFiles,1)
inShapeOld = shaperead([dataFolder char(inFiles.OldShape(i))]);
inPolyOld = polyshape([inShapeOld.X],[inShapeOld.Y], ‘Simplify’, false);
inShapeNew = shaperead([dataFolder char(inFiles.NewShape(i))]);
inPolyNew = polyshape([inShapeNew.X],[inShapeNew.Y], ‘Simplify’, false);
inPolyNewsub = intersect(inPolyNew, hucSub,’KeepCollinearPoints’,true);
inPolyOldsub = intersect(inPolyOld, hucSub);
[OutData(ii).intsecArea(i).Data, S] = polyIntersect(CoRegErrData, inPolyNewsub, inPolyOldsub);
OutData(ii).intsecArea(i).ID = char(inFiles.NewShape(i));
if ~isnan(S(1).X(1))
shapewrite(S, [dataFolder ‘outShapes_S’ hucID ‘_outInt_’ char(inFiles.NewShape(i))])
end
T = table(OutData(ii).intsecArea(i).Data, ‘VariableNames’, {‘outInt_acres1’ });
writetable(T, [dataFolder ‘outTables_S’ hucID ‘_outInt_’ char(inFiles.NewShape(i)) ‘.txt’])
endI have a MATLAB 2022 code that used the poly.intersect function–I can’t find in R2024 and need a workaround to compute the intersection of polygons. The code is below. In line 12 the polyIntersect function is used:
[OutData(ii).intsecArea(i).Data, S] = polyIntersect(CoRegErrData, inPolyNewsub, inPolyOldsub);
How do I modify the code in lieu of using polyIntersect ?
for ii = 1:length(hucPoly)
hucSub = polyshape(hucPoly(ii).X, hucPoly(ii).Y);
hucID = hucPoly(ii).Name;
OutData(ii).hucID = hucID;
for i = 1:size(inFiles,1)
inShapeOld = shaperead([dataFolder char(inFiles.OldShape(i))]);
inPolyOld = polyshape([inShapeOld.X],[inShapeOld.Y], ‘Simplify’, false);
inShapeNew = shaperead([dataFolder char(inFiles.NewShape(i))]);
inPolyNew = polyshape([inShapeNew.X],[inShapeNew.Y], ‘Simplify’, false);
inPolyNewsub = intersect(inPolyNew, hucSub,’KeepCollinearPoints’,true);
inPolyOldsub = intersect(inPolyOld, hucSub);
[OutData(ii).intsecArea(i).Data, S] = polyIntersect(CoRegErrData, inPolyNewsub, inPolyOldsub);
OutData(ii).intsecArea(i).ID = char(inFiles.NewShape(i));
if ~isnan(S(1).X(1))
shapewrite(S, [dataFolder ‘outShapes_S’ hucID ‘_outInt_’ char(inFiles.NewShape(i))])
end
T = table(OutData(ii).intsecArea(i).Data, ‘VariableNames’, {‘outInt_acres1’ });
writetable(T, [dataFolder ‘outTables_S’ hucID ‘_outInt_’ char(inFiles.NewShape(i)) ‘.txt’])
end I have a MATLAB 2022 code that used the poly.intersect function–I can’t find in R2024 and need a workaround to compute the intersection of polygons. The code is below. In line 12 the polyIntersect function is used:
[OutData(ii).intsecArea(i).Data, S] = polyIntersect(CoRegErrData, inPolyNewsub, inPolyOldsub);
How do I modify the code in lieu of using polyIntersect ?
for ii = 1:length(hucPoly)
hucSub = polyshape(hucPoly(ii).X, hucPoly(ii).Y);
hucID = hucPoly(ii).Name;
OutData(ii).hucID = hucID;
for i = 1:size(inFiles,1)
inShapeOld = shaperead([dataFolder char(inFiles.OldShape(i))]);
inPolyOld = polyshape([inShapeOld.X],[inShapeOld.Y], ‘Simplify’, false);
inShapeNew = shaperead([dataFolder char(inFiles.NewShape(i))]);
inPolyNew = polyshape([inShapeNew.X],[inShapeNew.Y], ‘Simplify’, false);
inPolyNewsub = intersect(inPolyNew, hucSub,’KeepCollinearPoints’,true);
inPolyOldsub = intersect(inPolyOld, hucSub);
[OutData(ii).intsecArea(i).Data, S] = polyIntersect(CoRegErrData, inPolyNewsub, inPolyOldsub);
OutData(ii).intsecArea(i).ID = char(inFiles.NewShape(i));
if ~isnan(S(1).X(1))
shapewrite(S, [dataFolder ‘outShapes_S’ hucID ‘_outInt_’ char(inFiles.NewShape(i))])
end
T = table(OutData(ii).intsecArea(i).Data, ‘VariableNames’, {‘outInt_acres1’ });
writetable(T, [dataFolder ‘outTables_S’ hucID ‘_outInt_’ char(inFiles.NewShape(i)) ‘.txt’])
end poly.intersect MATLAB Answers — New Questions

​