Closed kusterjs closed 1 year ago
Hi @kusterjs, I recently created a new way to define rates/airports in order to get rate by config instead of runway only https://github.com/rpuig2001/CDM/issues/75 ()
What would you think on adding a new item in order to define a list of dependent runways in the defined config?
Example:
AIRPORT:A:ArrRwyList:NotArrRwyList:D:DepRwyList:NotDepRwyList:DependendentRwyList:Rate_RateLvo
LEBL:A:24R,24L:*:D:24L:*:24L,24R:40_12
-> Runways 24L and 24R would be dependant. So, they will be in the same departure sequence.
LEBL:A:24R,24L:*:D:24L:*:*:40_12
-> No dependant runways.
Hey Roger
Yes, I think it might work that way. Just make sure to keep in mind that this dependent departure runway is not necessarily selected (in ES) as a departure runway. So it will only be the plugin config making that connection.
Yes,
It would only put them in the same list if aircrafts have the the runways assigned specified in the DependendentRwyList
. Not by Euroscope's runway selection.
Ok. Just for my understanding, the config only looks at the actual assigned runway and not the active runways in ES? Then what is the effect of multiple runways in DepRwyList
? Wouldn't this have the same result?
The dep/arr runway lists look at both assigned rwy for plane and assigned ES runway configuration. The mentioned for the DependendentRwyList only looks assigned runway for the planes.
Ok, thanks. Then I think the addition you proposed will fulfill our needs.
Btw, would it make sense to offer an option to host the rates file on a server as well? This could then also be combined with the CAD idea/data.
Yes, it would. I will think about it 👍
Because we have runway concepts with crossing departure runways, we would like an option to indicate this dependency. The issue is that these runways cannot be planned individually, but a departure on one runway will result in less capacity for the other runway. A simple assumption made can be to handle multiple runways in the same departure sequence (slot wise). An advanced version would be to allow an additional parameter to indicate the capacity changes connected to switching, but dependent runway. So that a mix of dependent runway can influence the departure capacity in addition (not only a simple replacement) as this might lower or also increase the total departure capacity. The full flexible version would be a definition of departure intervals based on runways or even down to the level of SIDs. But I doubt the required effort will pay off for such an implementation.