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
OwenArnold opened this issue
Sep 29, 2011
· 4 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
We should be able to clone a MDEW workspace in such a way that we also have the opportunity to modify the split into and split threshold parameters.
Providing that we are moving to a finer structure, we should be able to do this on a box by box basis and therefore prevent blowing up the memory. We could also ditch the events in the output workspace, or convert them from mdevents to mdlean events after the box structure has been created. The fact that boxes own events may also help us parallelize this algorithm.
Could we modify the split criteria, i.e. via a Strategy Pattern? For example split when Signal/Noise reatio meets some limit or when Signal is above threshold.
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 3880
We should be able to clone a MDEW workspace in such a way that we also have the opportunity to modify the split into and split threshold parameters.
The text was updated successfully, but these errors were encountered: