Many thanks indeed,l.
That has made things much simpler and personNumber/containerNumber behave
consistently with no dependence on the respective durations.
Yaay :)
-------- Original Message --------
On 12 Apr 2023, 12:33, Jakob Erdmann wrote:
> I fixed a few bugs related to triggered persons/containers. Please check
> whether you still find something odd after updating.
> Note, that 'expected' is only for persons whereas 'expectedContainers' is for
> containers.
>
> https://github.com/eclipse/sumo/issues/13015
> https://github.com/eclipse/sumo/issues/13016
> https://github.com/eclipse/sumo/issues/13017
>
> Am Di., 11. Apr. 2023 um 22:48 Uhr schrieb The div <[email protected]>:
>
>> Actually - more detail:
>>
>> In order for containers to trigger the truck departure when 'full' the
>> 'loadingDuration' for the truck has to be greater than that for the train.
>>
>> This is also true to trigger the bus departure, (in addition to needing to
>> have people waiting) ie the boardingDuration for the bus needs to be greater
>> than that for the train.
>>
>> I noticed this because I have multiple 'trains' with different
>> boarding/loading times and buses/trucks with constant values lower than some
>> of the trains. The effect being that triggering worked for some departures
>> but not for others!
>>
>> cheers
>> div
>>
>> ------- Original Message -------
>> On Tuesday, April 11th, 2023 at 18:51, The div <[email protected]> wrote:
>>
>>> Great!
>>> That has made my container loading much simpler, though person loading
>>> doesn't seem to work in the same way?
>>>
>>> I'm picking up containers and passengers from a stop on a lane
>>> If I set:
>>> containerNumber="16" (my 'full' value - the type containerCapacity = 100)
>>> triggered="container"
>>> expected="dummy" (I have no containers called 'dummy' )
>>>
>>> then the truck departure is triggered when "full", whether or not there are
>>> containers waiting when the truck stops. (Good.)
>>>
>>> If I try the same with person and a bus:
>>> personNumber="108" ( my 'full' value - the bus type personCapacity = 120 )
>>> triggered="person"
>>> expected="dummy"
>>>
>>> then the bus departure is triggered when 12 people are loaded - ie the
>>> spare capacity on the bus (personCapacity - personNumber) but only if those
>>> 12 people are waiting when the bus arrives. (bad) The trigger does not fire
>>> if people arrive after the bus stops.
>>> (It does fire if the expected equals a specific boarding person)
>>>
>>> Given the definitions of personNumber and containerNumber it feels like the
>>> bus behaviour is correct and the truck behaviour wrong? With the caveat
>>> that it should not require persons to be waiting in order for the trigger
>>> to fire?
>>>
>>> cheers
>>> div
>>>
>>> ------- Original Message -------
>>> On Tuesday, April 11th, 2023 at 13:02, Jakob Erdmann
>>> <[email protected]> wrote:
>>>
>>>> The following should work: add a dummy id to attribute `expected` and make
>>>> sure there are enough containers to load.
>>>> Once the train has been filled up to capacity it will ignore the trigger
>>>> and end the stop.
>>>> To only take up a specific amount you could set an initial count using
>>>> vehicle attribute `containerNumber`. These virtual containers are
>>>> subtracted from the capacity defined in the vType (but never show up as
>>>> distinct entities).
>>>>
>>>> Am Di., 11. Apr. 2023 um 13:47 Uhr schrieb The div <[email protected]>:
>>>>
>>>>> Thanks for that - have corrected my usage. :)
>>>>>
>>>>> I'm guessing that currently there is no way to trigger on multiple
>>>>> containers apart from specifying the individual container id's?
>>>>>
>>>>> ie I'd like to trigger depart when the vehicle is 'full' or has taken on
>>>>> a specific number of containers - listing them all is constraining when
>>>>> we're talking about a trainful!
>>>>>
>>>>> At the moment my solution is to use container flows to trigger a vehicle
>>>>> trip which has an initial stop at the triggering container stop. This
>>>>> allows it to take on the rest of the containers before departing.
>>>>>
>>>>> cheers
>>>>> div
>>>>> ------- Original Message -------
>>>>> On Tuesday, April 11th, 2023 at 08:30, Jakob Erdmann
>>>>> <[email protected]> wrote:
>>>>>
>>>>>> Note, that containerTriggered="true" and triggered="true" (for persons)
>>>>>> are the old (obsolete) form, since there are now additional things that
>>>>>> can be triggers.
>>>>>> Unfortunately, the documentation was incomplete until now. Please refer
>>>>>> to the updated description:
>>>>>> https://sumo.dlr.de/docs/Definition_of_Vehicles%2C_Vehicle_Types%2C_and_Routes.html#triggered_stops
>>>>>>
>>>>>> Am Mi., 5. Apr. 2023 um 14:38 Uhr schrieb The div <[email protected]>:
>>>>>>
>>>>>>> Was doing it wrong - misread the docs was using
>>>>>>> triggered="true" with expectedContainer=
>>>>>>>
>>>>>>> Should have been
>>>>>>> containerTriggered="true"
>>>>>>> :)
>>>>>>>
>>>>>>> -------- Original Message --------
>>>>>>> On 3 Apr 2023, 23:41, The div < [email protected]> wrote:
>>>>>>>
>>>>>>>> I don't know if this is a defect or if I'm doing this wrong - (sumo
>>>>>>>> 1.16 on windows 10)
>>>>>>>>
>>>>>>>> Scenario - Simulating a train journey where the start point loads
>>>>>>>> passengers and containers
>>>>>>>>
>>>>>>>> - Train trip from B to C with an initial stop at B
>>>>>>>>
>>>>>>>> - end of stop at B is triggered by a container -
>>>>>>>> expectedContainers="xx.9"
>>>>>>>>
>>>>>>>> ( my person flows are configured to complete before the container flow
>>>>>>>> completes. )
>>>>>>>>
>>>>>>>> Trip definition looks something like: (where TTT is a train with
>>>>>>>> person and container capacities specified)
>>>>>>>> <trip id="oops" type="TTT" depart="100" from="BBB" to="CCC" via=" DDD"
>>>>>>>> arrivalSpeed="53">
>>>>>>>> <stop lane="BBB_0" endPos="106" triggered="true"
>>>>>>>> expectedContainers="xx.9" />
>>>>>>>> <stop lane="YY_0" endPos="60" duration="60"/>
>>>>>>>> </trip>
>>>>>>>>
>>>>>>>> The .9 is because I have a number of containers (in this example: 10)
>>>>>>>> and I want to trigger departure once all containers are loaded
>>>>>>>>
>>>>>>>> - If passengers are loaded before containers, the stop ends when the
>>>>>>>> specified container is loaded. :.
>>>>>>>>
>>>>>>>> - If passengers are loaded after the specific container, with a gap,
>>>>>>>> the stop ends when all the passengers are loaded. Behaviour that may
>>>>>>>> be ok, but unexpected. :|
>>>>>>>>
>>>>>>>> - If no passengers are loaded the stop never ends. not good. :(
>>>>>>>>
>>>>>>>> - If I start the trip from A with a stop at B I get the same behaviour
>>>>>>>> - the stop never ends. :(
>>>>>>>>
>>>>>>>> - If I start the trip with passengers loaded (ie flow triggered) I
>>>>>>>> still need to load more passengers to end the stop, however under
>>>>>>>> these circumstances the train leaves as soon as 1 passenger is loaded
>>>>>>>> - leaving the others behind. :(
>>>>>>>>
>>>>>>>> (The UI parameter window shows "stop info" as "parking, triggered" . I
>>>>>>>> don't have 'parking="true" and setting parking="false" changes
>>>>>>>> nothing. )
>>>>>>>>
>>>>>>>> The implication is that I must have passengers boarding to have a
>>>>>>>> container triggered start point. I have also tried adding expected=""
>>>>>>>> with no effect.
>>>>>>>> Both passengers and containers are delivered to the train stop by bus
>>>>>>>> and truck respectively - with person and container flows defining the
>>>>>>>> end to end movement
>>>>>>>>
>>>>>>>> any thoughts welcome - this is just an experiment on my part so not
>>>>>>>> important.
>>>>>>>>
>>>>>>>> cheers
>>>>>>>> div
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> sumo-user mailing list
>>>>>>>> [email protected]
>>>>>>>> To unsubscribe from this list, visit
>>>>>>>> https://www.eclipse.org/mailman/listinfo/sumo-user
>>>>>
>>>>> _______________________________________________
>>>>> sumo-user mailing list
>>>>> [email protected]
>>>>> To unsubscribe from this list, visit
>>>>> https://www.eclipse.org/mailman/listinfo/sumo-user
>>
>> _______________________________________________
>> sumo-user mailing list
>> [email protected]
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user
