Class TrackerSystem

The data required for modeling a tracker system
These are the inputs to the tracker algorithm that is controlling
a set of trackers.

Namespace: SolarFarmerApi.Client

Syntax

public class TrackerSystem

Properties

EastWestGCR

East-West ground coverage ratio
Optional in the 2D case as the GCR from the Layout can be used.
Required for 3D models.

Declaration

public double? EastWestGCR { get; set; }

Property Value

Type	Description
System.Nullable<System.Double>

IsBacktracking

Is backtracking turned on for the tracker rotation algorithm?
Defaults to true.

Declaration

public bool? IsBacktracking { get; set; }

Property Value

Type	Description
System.Nullable<System.Boolean>

RotationMaxDeg

Maximum tracker rotation angle in degrees
This is defined in the system plane, so
the RotationMinDeg and RotationMaxDeg are typically
of the same magnitude even on an East-West slope.

Declaration

public double RotationMaxDeg { get; set; }

Property Value

Type	Description
System.Double

RotationMinDeg

Minimum tracker rotation angle in degrees
This is defined in the system plane, so
the RotationMinDeg and RotationMaxDeg are typically
of the same magnitude even on an East-West slope.

Declaration

public double RotationMinDeg { get; set; }

Property Value

Type	Description
System.Double

SystemPlaneAzimuth

The azimuth of any tilt in the system plane. In degrees from North.
The system plane is an imagined plane that in which all the tracker torque tubes sit.
If the terrain is flat then it is typically a horizontal plane. In that case the tilt will be
zero and the azimuth can take any value, it doesn't matter.
If the terrain is sloped, then typically the system plane will follow the slope of the underlying terrain.
If the terrain is undulating then typically the system plane will be an averaged slope over the array.
Ideally all the trackers in the tracker system will be placed in the system plane, but when the terrain is undulating
this may not be achieved. The 3D model in SolarFarmer allows can model the individual trackers locations in 3D,
so they can be placed off the system plane. In this case there may be row-to-row shading as the tracker algorithm
will not be correctly calculating the back-tracking.

Declaration

public double SystemPlaneAzimuth { get; set; }

Property Value

Type	Description
System.Double

SystemPlaneTilt

The tilt of the system plane, in degrees.
For example if the azimuth is 0 and the tilt is 10 then
the system plane will be tilted 10 degrees towards North.
See description of SystemPlaneAzimuth for more details.

Declaration

public double SystemPlaneTilt { get; set; }

Property Value

Type	Description
System.Double

TrackerAzimuth

The Azimuth of the trackers, in degrees.
Optional in the 2D case as the azimuth from the Layout can be used.
Required for 3D models.

Declaration

public double? TrackerAzimuth { get; set; }

Property Value

Type	Description
System.Nullable<System.Double>

UseSlopeAwareBacktracking

If true it uses slope-aware backtracking when calculating the rotation angles.
Defaults to true.

Declaration

public bool? UseSlopeAwareBacktracking { get; set; }

Property Value

Type	Description
System.Nullable<System.Boolean>