I need to solve this routing problem: two nodes cannot share the same route.
I.e.: if vehicle stop at node A, it shouldn't be allowed to stop also at node B, that means that node A and node B cannot be on the same route.
Any ideas?
Thanks in advance for your help.
Fabio
Did you try:
routing.solver().Add(routing.VehicleVar(index_a) != routing.VehicleVar(index_b))
Related
Would something like this work?
Basically what I am trying to do is to link an edge to a node but in return linking the node to an existing node but I need to query the node to find it to link it.
here -[people_link(id="123")]-> node::person(name==w);
This should work in version 1.4 of Jaseci. Try somethign like
here +[people_link(id="123")]+> node::person(name==w);
I want to create a new Agent out of a database. The agent should have several parameters like material type, length, ect.
My Problem is, that i get a lot of errors, trying to define my agent with java code. I think the problem results out of line 868 and 869 in my main code. AnyLogic has a problem defining the VALUE of an agent trough a code block.
So how can I "delete" or remove the
Agent _value; _value = ?
Here's a picture: enter image description here
I have seen a program like mine in the past WITHOUT these two lines. So I know it's possible, but I don't know how. Can anyone please help me? Thanks in advance.
Do not instantiate agents using MyAgent newAgent = new MyAgent(...)
Always instantiate agents into (empty) populations using add_MyAgentPopulation(...)
I have defined a UnitMonitor of type CheckNTServiceStateMonitorType. The AlertSeverity of this Monitor depends on an attribute of the class being monitored, so it is dynamically specified.
However, I I could find no way to set the AlertSeverity dynamically. For instances:
<AlertSettings>
<AlertSeverity>
$Target/Property[MyMonitoredClass]/AlertSeverity$
<AlertSeverity>
</AlertSettings>
Is there any way to accomplish this?
You cannot do it for a Unit Monitor. Such feature is only available for Rules.
Cheers
Max
I'm new to OSRM and doing some research. As per the title, is it possible to restrict routing based on traffic_calming tags? For instance, could you add "traffic_calming" somewhere in "profiles/car.lua" or in "features/car/barrier.feature" such that when the routing was done it avoided some/all of roads with traffic calming on them?
Thanks
Yes you can mark traffic_calming as barrier by adding some code here:
result.barrier = node:get_value_by_key("traffic_calming") == "yes"
I have the following tree:
1-[HAS]->2-[HASSUBPAGE]->3-[HASSUBPAGE]->4
Now I want to traverse this tree starting at 4 and go up to 1 with this traverser (postng to /db/data/node/4/traverse/node):
{"order":"breadth_first","uniqueness":"node_path","relationships":[{"type":"HASSUBPAGE","direction":"in"},{"type":"HAS","direction":"in"}]}
But it stops at node 3 so all I get is node 3.
Any Ideas, why?
You must provide the max_depth parameter, as it defaults to 1 (to prevent infinite traversals).
Please try that and report if it worked for you.