Parking assignment - Revision history

BASys at 21:44, 9 August 2011

2011-08-09T21:44:08Z

← Older revision		Revision as of 16:44, 9 August 2011
Line 1:		Line 1:
	{{Infobox-Applicable-FSVersion		{{Infobox-Applicable-FSVersion
	\| FSXI = ~~true~~		\| FSXI = false
	\| FSXA = true		\| FSXA = true
	\| FSX = true		\| FSX = true

Alexf: ce

2010-12-26T11:58:54Z

← Older revision		Revision as of 06:58, 26 December 2010
Line 10:		Line 10:
	== Introduction ==		== Introduction ==

	In order to find a parking spot FSX ~~while~~ scan through all ~~parkings~~ at the given airport.		In order to find a parking spot FSX will scan through all parking spots at the given airport.

	For each parking it will check if it is occupied and skip it if it is already assigned.		For each parking it will check if it is occupied and skip it if it is already assigned.

	It will also retrieve the wingspan of the plane, divide it by two and use the next largest integer value to determine if the parking is large enough. For example: wing span = 32.9 meters, 32.9 ~~divived~~ by two is 16.45, FSX will check if the radius of the parking is 17 meters or larger. ~~Parkings~~ that are too small will be skipped. ''[TODO: what value is used for vehicles / planes without wingspan specified]''		It will also retrieve the wingspan of the plane, divide it by two and use the next largest integer value to determine if the parking is large enough. For example: wing span = 32.9 meters, 32.9 divided by two is 16.45, FSX will check if the radius of the parking is 17 meters or larger. Parking spots that are too small will be skipped. ''[TODO: what value is used for vehicles / planes without wingspan specified]''

	If the parking is available and large enough it will call the scoring function. In the end the parking with the smallest score will be selected.		If the parking is available and large enough it will call the scoring function. In the end the parking with the smallest score will be selected.

Denial: /* Parking Type */

2010-02-05T12:12:36Z

Parking Type

← Older revision		Revision as of 07:12, 5 February 2010
Line 66:		Line 66:
	! dock		! dock
	! vehicle		! vehicle
	! ~~parking~~		! fuel
	\|- align=center		\|- align=center
	\| align=left \| ramp \|\| 0\|\| 2\|\| 4\|\| 5\|\| 3\|\| 10\|\| 10\|\| 10		\| align=left \| ramp \|\| 0\|\| 2\|\| 4\|\| 5\|\| 3\|\| 10\|\| 10\|\| 10

BASys: Navbox-Traffic-Related added

2010-02-02T13:05:02Z

Navbox-Traffic-Related added

← Older revision		Revision as of 08:05, 2 February 2010
Line 148:		Line 148:
	The same scores are used, but the order in which they are evaluated differs. In this case the parking name is most important. This ofcourse is because the user actually selects a specific parking name (GATE, PARKING) from the ATC menu. Next the type is taken in to account and then the ICAO code. The ICAO code thus has a much lower weight for the user plane. Again, the final score that is evaluated is the radius, the smallest fitting parking will be assigned.		The same scores are used, but the order in which they are evaluated differs. In this case the parking name is most important. This ofcourse is because the user actually selects a specific parking name (GATE, PARKING) from the ATC menu. Next the type is taken in to account and then the ICAO code. The ICAO code thus has a much lower weight for the user plane. Again, the final score that is evaluated is the radius, the smallest fitting parking will be assigned.


			== Related ==

			=== Internal ===
			{{Template:Navbox-Traffic-Related}}

			=== External ===
	[[category:Airport_Design]]		[[category:Airport_Design]]

BASys: FSVersion infobox added

2010-02-02T12:59:33Z

FSVersion infobox added

← Older revision		Revision as of 07:59, 2 February 2010
Line 1:		Line 1:
			{{Infobox-Applicable-FSVersion
			\| FSXI = true
			\| FSXA = true
			\| FSX = true
			\| FS2004 = false
			\| FS2002 = false
			\| FS2000 = false
			\| FS98 = false
			}}
	== Introduction ==		== Introduction ==

Denial: /* Parking Type */

2010-02-02T12:06:17Z

Parking Type

← Older revision		Revision as of 07:06, 2 February 2010
Line 97:		Line 97:
	\| 5		\| 5
	\| 0		\| 0
	~~\| 10~~
	~~\| 10~~
	~~\| 10~~
	~~\|- align=center~~
	~~\| align=left \| mil_cargo~~
	~~\| 2~~
	~~\| 3~~
	~~\| 0~~
	~~\| 1~~
	~~\| 4~~
	\| 10		\| 10
	\| 10		\| 10
Line 119:		Line 109:
	\| 4x255		\| 4x255
	\|-		\|-
			\|+ Scores for actual parking type versus requested parking type, lower is better
	\|}		\|}

Denial: /* Introduction */

2010-02-02T12:00:53Z

Introduction

← Older revision		Revision as of 07:00, 2 February 2010
Line 5:		Line 5:
	For each parking it will check if it is occupied and skip it if it is already assigned.		For each parking it will check if it is occupied and skip it if it is already assigned.

	It will also retrieve the wingspan of the plane, divide it by two and use the next largest integer value to determine if the parking is large enough. ~~FOr~~ example: wing span = 32.9 meters. 32.9 divived by two is 16.45. FSX will check if the radius of the parking is 17 meters or larger. Parkings that are too small will be skipped. ''[TODO: what value is used for vehicles / planes without wingspan specified]''		It will also retrieve the wingspan of the plane, divide it by two and use the next largest integer value to determine if the parking is large enough. For example: wing span = 32.9 meters, 32.9 divived by two is 16.45, FSX will check if the radius of the parking is 17 meters or larger. Parkings that are too small will be skipped. ''[TODO: what value is used for vehicles / planes without wingspan specified]''

	If the parking is available and large enough it will call the scoring function. In the end the parking with the smallest score will be selected.		If the parking is available and large enough it will call the scoring function. In the end the parking with the smallest score will be selected.

Denial at 07:44, 2 February 2010

2010-02-02T07:44:24Z

← Older revision		Revision as of 02:44, 2 February 2010
Line 10:		Line 10:

	The scoring function itself takes several inputs: the requested parking name, the requested parking types, the requested radius, the requested ICAO codes and a flag that indicates whether the request is for a user or AI plane.		The scoring function itself takes several inputs: the requested parking name, the requested parking types, the requested radius, the requested ICAO codes and a flag that indicates whether the request is for a user or AI plane.

			== Scoring ==

	In the scoring function 4 individual scores will be determined for: radius, name, type and ICAO.		In the scoring function 4 individual scores will be determined for: radius, name, type and ICAO.

	== Radius ==		=== Radius ===

	The requested radius is subtracted from the actual radius. The smaller the result, the more likely the parking will be selected. FSX thus looks for a parking that is just large enough. An additional check is performed and I'm not sure what is done exactly. The parking is checked for the presence of a subobject and if one is found the score will be increased by one. One possibility is that this is the check for a jetway, in the scenery or actually on display for the current settings. I'm not sure, since this will mean that for two otherwise equal parkings the one without a jetway will be selected.		The requested radius is subtracted from the actual radius. The smaller the result, the more likely the parking will be selected. FSX thus looks for a parking that is just large enough. An additional check is performed and I'm not sure what is done exactly. The parking is checked for the presence of a subobject and if one is found the score will be increased by one. One possibility is that this is the check for a jetway, in the scenery or actually on display for the current settings. I'm not sure, since this will mean that for two otherwise equal parkings the one without a jetway will be selected.
Line 19:		Line 21:
	The resulting score is then limited to the range 0..255.		The resulting score is then limited to the range 0..255.

	== Parking Name ==		=== Parking Name ===

	The requested parking name appears to be limited to PARKING, GATE, DOCK and NONE. The parking name of the parking currently being evaluated is retrieved. If the request is NONE or above the maximum definded parking name (25 = GATE_Z) the score will be 0. A score of 0 is also assigned if there is an exact match between the request and the actual name.		The requested parking name appears to be limited to PARKING, GATE, DOCK and NONE. The parking name of the parking currently being evaluated is retrieved. If the request is NONE or above the maximum definded parking name (25 = GATE_Z) the score will be 0. A score of 0 is also assigned if there is an exact match between the request and the actual name.
Line 35:		Line 37:
	** Else the score will be 10 (DOCK, all PARKING names)		** Else the score will be 10 (DOCK, all PARKING names)

	== Parking Type ==		=== Parking Type ===

	This is where it gets a bit tricky. Again, the actual value is compared to the requested value. If no types are in the request the score will be 0, unless the actual type is VEHICLE, then the function will return all 255's.		This is where it gets a bit tricky. Again, the actual value is compared to the requested value. If no types are in the request the score will be 0, unless the actual type is VEHICLE, then the function will return all 255's.
Line 119:		Line 121:
	\|}		\|}

	== ICAO Code ==		=== ICAO Code ===

	For the ICAO code two lists will be matched, the list of codes for the parking and that for the plane.		For the ICAO code two lists will be matched, the list of codes for the parking and that for the plane.

Denial: added table

2010-02-02T07:43:32Z

added table

@@ Line 43: / Line 43: @@
 If no match is found the first listed type will be used for further evaluation.
-The different types that are evaluated are: RAMP, CARGO, MIL_CARGO, MIL_COMBAT, GATE, DOCK, VEHICLE, FUEL [not 100% sure, but VEHICLE is the highest value from the SDK and in the code an additional one is checked which I assume to be FUEL). (Remember that exact matches were already taken care of with a score of 0)
+The different types that are evaluated are: RAMP, CARGO, MIL_CARGO, MIL_COMBAT, GATE, DOCK, VEHICLE, FUEL ''[not 100% sure, but VEHICLE is the highest value from the SDK and in the code an additional one is checked which I assume to be FUEL]''. (Remember that exact matches were already taken care of with a score of 0)
-* Request RAMP: Actual: Cargo 2, Mil_cargo 4, Mil_combat 5, Gate 3, Dock 10, Vehicle 10, Fuel 10
+{| class="wikitable" border="1"
-* Request CARGO: Actual: Ramp 1, Mil_cargo 3, Mil_combat 4, Gate 2, Dock 10, Vehicle 10, Fuel 10
+|-
-* Request MIL_CARGO: Actual: Ramp 2, Cargo 3, Mil_combat 1, Gate 4, Dock 10, Vehicle 10, Fuel 10
+!  request / actual:
-* Request MIL_COMBAT: Actual: Ramp 2, Cargo 3, Mil_cargo 1, Gate 4, Dock 10, Vehicle 10, Fuel 10
+!  ramp
-* Request GATE: Actual: Ramp 3, Cargo 2, Mil_cargo 4, Mil_combat 5, Dock 10, Vehicle 10, Fuel 10
+!  cargo
-* Request DOCK: Function will return scores 255, 255, 255, 255
+!  mil_cargo
-* Request VEHICLE: Function will return scores 255, 255, 255, 255 unless actual type is Vehicle, then the score will be 0
+!  mil_combat
 == ICAO Code ==

Denial: A description of how FSX assigns a parking

2010-02-01T23:01:01Z

A description of how FSX assigns a parking

New page

== Introduction ==

In order to find a parking spot FSX while scan through all parkings at the given airport.

For each parking it will check if it is occupied and skip it if it is already assigned.

It will also retrieve the wingspan of the plane, divide it by two and use the next largest integer value to determine if the parking is large enough. FOr example: wing span = 32.9 meters. 32.9 divived by two is 16.45. FSX will check if the radius of the parking is 17 meters or larger. Parkings that are too small will be skipped. ''[TODO: what value is used for vehicles / planes without wingspan specified]''

If the parking is available and large enough it will call the scoring function. In the end the parking with the smallest score will be selected.

The scoring function itself takes several inputs: the requested parking name, the requested parking types, the requested radius, the requested ICAO codes and a flag that indicates whether the request is for a user or AI plane.

In the scoring function 4 individual scores will be determined for: radius, name, type and ICAO.

== Radius ==

The requested radius is subtracted from the actual radius. The smaller the result, the more likely the parking will be selected. FSX thus looks for a parking that is just large enough. An additional check is performed and I'm not sure what is done exactly. The parking is checked for the presence of a subobject and if one is found the score will be increased by one. One possibility is that this is the check for a jetway, in the scenery or actually on display for the current settings. I'm not sure, since this will mean that for two otherwise equal parkings the one without a jetway will be selected.

The resulting score is then limited to the range 0..255.

== Parking Name ==

The requested parking name appears to be limited to PARKING, GATE, DOCK and NONE. The parking name of the parking currently being evaluated is retrieved. If the request is NONE or above the maximum definded parking name (25 = GATE_Z) the score will be 0. A score of 0 is also assigned if there is an exact match between the request and the actual name.

If not, which is in most cases (eg. request: GATE actual: GATE_D), the following will happen:

* If the request is DOCK:
**The function will return immediately with all four individual scores at 255.
* If the request is PARKING:
** If the actual name is NONE or GATE, DOCK, GATE_... the score will be 10
** If the actual name is PARKING the score will be 0
** Else the score will be 1 (actual name is N_PARKING, NE_PARKING, ....)
* If the request is GATE:
** If the actual name is GATE or GATE_....: for an exact match the score will be 0, else it will be 1. SO if the actual is GATE_K and the request is GATE_K, the score will be 0. But as mentioned before, I'm not sure if there ever will be a specific gate request.
** Else the score will be 10 (DOCK, all PARKING names)

== Parking Type ==

This is where it gets a bit tricky. Again, the actual value is compared to the requested value. If no types are in the request the score will be 0, unless the actual type is VEHICLE, then the function will return all 255's.

If there are requests the actual type will be compared to each of them, if a match is found the score will be the index of the match (0 based). This implies that the order of codes entered in the aircraft.cfg is important. (As mentioned in the SDK).

If no match is found the first listed type will be used for further evaluation.

The different types that are evaluated are: RAMP, CARGO, MIL_CARGO, MIL_COMBAT, GATE, DOCK, VEHICLE, FUEL [not 100% sure, but VEHICLE is the highest value from the SDK and in the code an additional one is checked which I assume to be FUEL). (Remember that exact matches were already taken care of with a score of 0)

* Request RAMP: Actual: Cargo 2, Mil_cargo 4, Mil_combat 5, Gate 3, Dock 10, Vehicle 10, Fuel 10
* Request CARGO: Actual: Ramp 1, Mil_cargo 3, Mil_combat 4, Gate 2, Dock 10, Vehicle 10, Fuel 10
* Request MIL_CARGO: Actual: Ramp 2, Cargo 3, Mil_combat 1, Gate 4, Dock 10, Vehicle 10, Fuel 10
* Request MIL_COMBAT: Actual: Ramp 2, Cargo 3, Mil_cargo 1, Gate 4, Dock 10, Vehicle 10, Fuel 10
* Request GATE: Actual: Ramp 3, Cargo 2, Mil_cargo 4, Mil_combat 5, Dock 10, Vehicle 10, Fuel 10
* Request DOCK: Function will return scores 255, 255, 255, 255
* Request VEHICLE: Function will return scores 255, 255, 255, 255 unless actual type is Vehicle, then the score will be 0

== ICAO Code ==

For the ICAO code two lists will be matched, the list of codes for the parking and that for the plane.

If no codes are present in the request (as in: no codes in the aircraft.cfg):

* If the parking has no codes the score will be 0.
* If the parking has codes the score will be 255.

If the request has codes:

* If the parking has no codes, the score will be 254.
* If the parking has codes the lists will be matched. The score will depend on the indices of the match: 2 * index of match in list of parking codes + 1 * index of match in list of plane codes.

''[TODO: What is the score if there is no match, I guess at least 253]''
''[TODO: Which list is in the outerloop? Are all the plane codes checked vs the first parking code and then the second, or are all the parking codes checked vs the first plane code.]''

== Combining the scores for AI ==

At this point there will be four individual scores 0..255. For an AI request these will be combined to a single unsigned integer in this sequence: ICAO, Type, Name, Radius. In other words for AI the ICAO matching is most important. If several parkings give the same score for the ICAO code, the requested type will determine which one is assigned. If there are still parkings with an equal score, the parking name will decide. ''[TODO: What determines the requested name, is it always GATE, it is not controlled by the aircraft.cfg]'' If there are still multiple options available, the smallest parking will be assigned. Possibly, if there are several that are the smallest precedence might be given to one without a jetway ''[Unconfirmed]''.

If the score for several parkings is completely identical, the first one encountered will be selected. This can still vary as the function that scans through the parkings does not start the scan at index 0, but somewhere in the middle and then wraps around. ''[TODO: What determines the first parking evaluated: random, last parking found?]''

== Combining the scores for the user plane ==

The same scores are used, but the order in which they are evaluated differs. In this case the parking name is most important. This ofcourse is because the user actually selects a specific parking name (GATE, PARKING) from the ATC menu. Next the type is taken in to account and then the ICAO code. The ICAO code thus has a much lower weight for the user plane. Again, the final score that is evaluated is the radius, the smallest fitting parking will be assigned.

[[category:Airport_Design]]