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
AndreiSavici opened this issue
May 1, 2015
· 2 comments
Assignees
Labels
FrameworkIssues and pull requests related to components in the FrameworkStaleThis label is automatically applied to issues that are automatically closed by the stale bot
CutMD creates a W matrix. That is fine, as long as the original workspace was [H,0,0],[0,K,0],[0,0,L]. The labels are also relying on this assumption. But one might create an original workspace with uProj=1,1,0; vProj=-1,1,0; wProj=0,0,1. Then labels are wrong, and W matrix also needs to be recalculated
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.
To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.
stalebot
added
the
Stale
This label is automatically applied to issues that are automatically closed by the stale bot
label
Feb 24, 2021
FrameworkIssues and pull requests related to components in the FrameworkStaleThis label is automatically applied to issues that are automatically closed by the stale bot
This issue was originally TRAC 11687
CutMD creates a W matrix. That is fine, as long as the original workspace was [H,0,0],[0,K,0],[0,0,L]. The labels are also relying on this assumption. But one might create an original workspace with uProj=1,1,0; vProj=-1,1,0; wProj=0,0,1. Then labels are wrong, and W matrix also needs to be recalculated
The text was updated successfully, but these errors were encountered: