8:22 p.m.
Add API to allow globals to be specified for the working memory
---------------------------------------------------------------
Key: JBRULES-3329
URL: https://issues.jboss.org/browse/JBRULES-3329
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Mark Proctor
Provide an API to allow globals to be specified to be inserted into the working memory.
This would allow customisation of things like constraint costs. Although this could be
done by non-global facts being inserted, performance would be better using a global rather
than requiring an instance fact to be matched.
Discussions with Ge0ffrey on IRC revealed that more than 1 working memory exists, and in
fact in future versions supporting multithreading or GAs, they may well be many more than
one WM, so we need an API that will inject the global into all instances of the WM, just
like the global cost constraint global is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:24 p.m.
[
https://issues.jboss.org/browse/JBRULES-3329?page=com.atlassian.jira.plug...
]
Geoffrey De Smet reassigned JBRULES-3329:
-----------------------------------------
Assignee: Geoffrey De Smet (was: Mark Proctor)
Add API to allow globals to be specified for the working memory
---------------------------------------------------------------
Key: JBRULES-3329
URL: https://issues.jboss.org/browse/JBRULES-3329
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Geoffrey De Smet
Provide an API to allow globals to be specified to be inserted into the working memory.
This would allow customisation of things like constraint costs. Although this could be
done by non-global facts being inserted, performance would be better using a global rather
than requiring an instance fact to be matched.
Discussions with Ge0ffrey on IRC revealed that more than 1 working memory exists, and in
fact in future versions supporting multithreading or GAs, they may well be many more than
one WM, so we need an API that will inject the global into all instances of the WM, just
like the global cost constraint global is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:06 p.m.
[
https://issues.jboss.org/browse/JBRULES-3329?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-3329:
-------------------------------------------
Could you comment an example of a use case that would benefit for global injection?
I'd like to understand the real use cases for this to implement/test it better.
If we reuse the same instance for all the threads, then that global instance needs to be
thread-safe, is suspect to congestion and clustering will fail outright. (Note:
multi-threading and clustering are design atm, not implementation.)
So I 'd rather see a factory for such a global instance, but that means the global
cannot output data after the Solver is done. Is that a problem?
Add API to allow globals to be specified for the working memory
---------------------------------------------------------------
Key: JBRULES-3329
URL: https://issues.jboss.org/browse/JBRULES-3329
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Geoffrey De Smet
Provide an API to allow globals to be specified to be inserted into the working memory.
This would allow customisation of things like constraint costs. Although this could be
done by non-global facts being inserted, performance would be better using a global rather
than requiring an instance fact to be matched.
Discussions with Ge0ffrey on IRC revealed that more than 1 working memory exists, and in
fact in future versions supporting multithreading or GAs, they may well be many more than
one WM, so we need an API that will inject the global into all instances of the WM, just
like the global cost constraint global is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:37 p.m.
[
https://issues.jboss.org/browse/JBRULES-3329?page=com.atlassian.jira.plug...
]
David Glassborow commented on JBRULES-3329:
-------------------------------------------
So an example is constraint costs. I'm looking at this for scheduling field workers,
both what work, and what order, over a large amount of work and workers.
For some sorts of work, being late is very expensive (for example where they are meeting a
member of the public, and by law they have to be on time or there are financial
penalties), where as for others the primary factor is travel time (when there are number
of small pieces of work to do and travel costs dominate).
These scaling factors between the different constraints need to be adjustable between
runs, because they need to be adjustable per business area.
As we discussed on IRC, these could be done by inserting facts, but that is going to slow
and verbose for constantly looking them up as part of the rules.
Make sense ?
Add API to allow globals to be specified for the working memory
---------------------------------------------------------------
Key: JBRULES-3329
URL: https://issues.jboss.org/browse/JBRULES-3329
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Geoffrey De Smet
Provide an API to allow globals to be specified to be inserted into the working memory.
This would allow customisation of things like constraint costs. Although this could be
done by non-global facts being inserted, performance would be better using a global rather
than requiring an instance fact to be matched.
Discussions with Ge0ffrey on IRC revealed that more than 1 working memory exists, and in
fact in future versions supporting multithreading or GAs, they may well be many more than
one WM, so we need an API that will inject the global into all instances of the WM, just
like the global cost constraint global is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 p.m.
[
https://issues.jboss.org/browse/JBRULES-3329?page=com.atlassian.jira.plug...
]
David Glassborow commented on JBRULES-3329:
-------------------------------------------
Related post:
http://stackoverflow.com/questions/6855209/setting-global-variables-in-wo...
Your point in that posting about delta based scoring is important. If this anyway to make
delta based scoring still work if the global returns a cost for the cost factor ? or an
injected global is the constant ?
Add API to allow globals to be specified for the working memory
---------------------------------------------------------------
Key: JBRULES-3329
URL: https://issues.jboss.org/browse/JBRULES-3329
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Geoffrey De Smet
Provide an API to allow globals to be specified to be inserted into the working memory.
This would allow customisation of things like constraint costs. Although this could be
done by non-global facts being inserted, performance would be better using a global rather
than requiring an instance fact to be matched.
Discussions with Ge0ffrey on IRC revealed that more than 1 working memory exists, and in
fact in future versions supporting multithreading or GAs, they may well be many more than
one WM, so we need an API that will inject the global into all instances of the WM, just
like the global cost constraint global is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:28 p.m.
[
https://issues.jboss.org/browse/JBRULES-3329?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-3329:
-------------------------------------------
That's really a user mailing list question. But I don't see the interference with
delta scoring as the global is set before the solver starts and never changes during
solving. I prefer the alternative: see InstitutionalWeightings in the examination
example.
Add API to allow globals to be specified for the working memory
---------------------------------------------------------------
Key: JBRULES-3329
URL: https://issues.jboss.org/browse/JBRULES-3329
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Geoffrey De Smet
Provide an API to allow globals to be specified to be inserted into the working memory.
This would allow customisation of things like constraint costs. Although this could be
done by non-global facts being inserted, performance would be better using a global rather
than requiring an instance fact to be matched.
Discussions with Ge0ffrey on IRC revealed that more than 1 working memory exists, and in
fact in future versions supporting multithreading or GAs, they may well be many more than
one WM, so we need an API that will inject the global into all instances of the WM, just
like the global cost constraint global is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4624
days inactive
4661
days old
5 comments
4 participants
participants (4)
-
David Glassborow (Created) (JIRA) -
David Glassborow (JIRA)
-
Geoffrey De Smet (Assigned) (JIRA)
-
Geoffrey De Smet (JIRA)