Module Reference: TestFlightCore

TestFlightCore

Properties

• configuration - see Advanced-Configuration-Syntax

• maxData - the amount of data needed to fully test the part. Defaults to largest key in all the part's reliabilityCurves.

• startFlightData - data provided "for free". Defaults to 0.

• techTransfer - applies data collected from related parts to this one. Applied once when a part is first flown. Does not stack with startFlightData.

  This is a string consisting of one or more branches (separated by "&"), each branch consisting of one or more parts (separated by ",") and a transfer percentage. Parts can be identified either by part name, full name, or configuration name. If multiple parts are listed for each branch, the first part is considered the previous generation, with subsequent parts considered older and less relevant (see techTransferGenerationPenalty, below). Data from all parts on all branches are added together.

  For example, rs-27a,rs-27,h1-b,h1:10&lr-89-na-7,lr-89-na-6,lr-89-na-5:25 defines two branches, one from the RS-27 branch (10% of data transferred) and one from the LR-89 branch (25% transferred).

• techTransferGenerationPenalty - the fraction of data lost, per extra generation, when transferring data from multiple parts in a branch. The default is 0.05, meaning the second part on the branch has 95% of its value, the third has 90%, and so on.

• failureRateModifier - scaling factor for this part's Base Failure Rate, after all other modifiers have been applied. Defaults to 1.

• rndRate - scaling factor for amount of data produced each R&D cycle. Defaults to 1.

• rndCost - scaling factor for funds consumed each R&D cycle. Defaults to 1.

• rndMaxData - the maximum amount of data that can be acquired through lab R&D. Defaults to 75% of maxData.

• scienceDataValue - makes tech tree nodes cost less to research if one or more of their parts have already flown. The value is the amount of Science saved if this part were fully tested. Defaults to 0.

Description

TestFlightCore is the main manager of TestFlight on a specific part and handles all of the coordination and logic for TestFlight on that part.

There can only ever be a single TestFlightCore module on a part