caskade-planner's People
caskade-planner's Issues
Set initial state to properties
Currently we set the initial state to all properties. Logically, we should set the initial state only for the inputs. If we do not set the initial state on the output, these are free variables and fulfill all requirements from the beginning and no capability has to be executed. Here we need to consider how to avoid this problem.
Set all init values that are not explicitly defined to false / 0
Currently, we only set explicitly defined values in the init stage. There should be default initilization:
- all bools that are not set -> false
- all reals that are not set -> 0
Consider capability together with resource
For planning, we cannot look at a capability without looking at the resources providing this capability.
Event if two resources A and B provide the same capability, resource properties influence the planning solution. For example, one resource could have enough material while the others stock is empty.
We need to take the combination of resource and capability into account for planning.
Example: Resources A and B offer Drilling. Instead of a variable Drilling
, we need two variables A_Drilling
and B_Drilling
.
Resource-dependent sequence of capabilities
The capabilities lack a concrete reference to a resource. If resource X grabs a package, resource Y cannot transport the package. Current preconditions are not sufficient to prevent such a solution.
Propagation of desired values from input information
Propagation of desired values from input information prevent repeated execution of the corresponding capability. A solution must be found here: For example, all desired values of input information, i.e. instance descriptions with no expression goal, could remain free and not be propagated across events and happenings.
Propagation of properties across capabilities
For some capabilites, properties that are relevant for other properties are irrelevant. Nevertheless, the properties of a product must be retained across the application of capabilities, as they may be relevant again for a later capability and the information should not be lost. Currently, when modeling the ontology, it is always necessary to model all properties for each capability.
Query Checking
We need to check if all the queries are necessary. Don't we already have the necessary information in the classes or do we have queries that query very similar content?
Queries only once for all happenings
We can assume that there is no change to the ontology once planning is started. Thus, every query should be fired only once overall. NOT once per happening as we do now.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.