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
FrameworkIssues and pull requests related to components in the FrameworkStaleThis label is automatically applied to issues that are automatically closed by the stale bot
SliceMD currently goes through the whole MD workspace and analyses every event, present in the workspace if the one needs to be added to the target workspace. This makes it an order of magnitude slower then Horace for workspaces with number of events much bigger then number of boxes
More intelligent approach is implemented by BinMD, which checks the boxes first and if the box with large number of events is outside of the cut limits, the box is rejected outright.
Similar algorithm should be deployed by SliceMD
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 8013
SliceMD currently goes through the whole MD workspace and analyses every event, present in the workspace if the one needs to be added to the target workspace. This makes it an order of magnitude slower then Horace for workspaces with number of events much bigger then number of boxes
More intelligent approach is implemented by BinMD, which checks the boxes first and if the box with large number of events is outside of the cut limits, the box is rejected outright.
Similar algorithm should be deployed by SliceMD
The text was updated successfully, but these errors were encountered: