Input parameters Sample Clauses

Input parameters. All simulations were run for 50 years with 100 iterations using VORTEX version 9.99c. Input parameters for the baseline model were as follows:  Definition of extinction Extinction was defined as the complete absence of one or other sex.
Sample 1Sample 2
AutoNDA by SimpleDocs
Input parameters. There are several equations in this section of the proposal outlining the calculation for a default energy bid for storage resources. Some of these equations include variables that characterize costs that are specific to individual resources. CAISO contends that these values are relatively stable over time, but also are generally unknown to the CAISO. Similar to existing gas resources today, XXXXX plans to collect this data for all storage resources in the future. This data will be collected via CAISO master file process that is already in place to capture resource specific data. Master File variables that will be collected for storage resources: η: Round-trip efficiency 𝛿: Storage duration for the resource (i.e. 4 hours) 𝜌: Cell degradation cost Like other variables that are collected and stored in master file, scheduling coordinators for these resources will have requirements for submitting these variables to CAISO. As with other master file data, XXXXX will have descriptions of what this data should represent, how the data should be submitted and what, if any, documentation should accompany this data when it is submitted to master file. Finally, as with all data submitted to CAISO, there will be an obligation for scheduling coordinators to ensure that this data is up to date and accurate for all resources. CAISO collects round trip efficiency values today through the master file for each storage resource on the system. XXXXX does not envision any changes to this process in the future. The ISO also collects the maximum amount of storage capability (in MWh) for each storage resource, this value combined with the resource Pmax value, will inform the storage duration parameter above.
Sample 1
Input parameters. In the simulation the following policy instruments can be selected. How do you judge their relevance for the question of supporting the uptake of photovoltaic in the Xxxxxx Romagna region? Not relevant at all Very relevant Investment Grants Feed-­‐In-­‐Tariffs Interest Rate Subsidies Can you think of any other policy instruments that might be useful in this context? Which? Besides the selection of policy instruments the factors mentioned below could be provided as inputs for the simulating the PV uptake. How do you judge the relevance of these? Overall Budget Time frame Not relevant at all Very relevant Budget distribution over time Geographical region to be analyzed Can you think of any other input parameters that might be useful? Which? Output Parameters The list below indicates the outputs from the simulation. How do you judge the relevance of these outputs? Not relevant at all Very relevant Number of households with PV installations at certain point in time Geographical distribution of PV installations Number of households with PV installations over time Spatial/Geographic distribution of PV installations over time Amount of energy produced Cost distribution over time Can you think of any other combinations of output information you would want to analyse? Which? On which granularity level would you like to view the information? Individual Household Level City/Town Level Provincial Level Regional Level National Level Other: Can you specify use cases that exemplify a possible task that can be addressed via the simulation model? (Find an example below)
Sample 1
Input parameters. There are five input parameters describing the robotic application: velocity, predominant movement type, tool, distance from the robot, and type of HRI. The graphical design of the toolkit is presented on Figure X.
Sample 1
Input parameters. Although defined in the metadata and the APIs, input parameter values may be input by an end-user to configure the execution of a particular service. Name standardisation - according with the metadata and API - reduces the chance of error and thus provides the end-user with a more robust and reliable service leading to greater satisfaction and increased usage with confidence.
Sample 1
Input parameters. The preliminary specification for the optical input into the Amplifier is as follows:
Sample 1

Related to Input parameters

  • Measuring EPP parameters Every 5 minutes, EPP probes will select one “IP address” of the EPP servers of the TLD being monitored and make an “EPP test”; every time they should alternate between the 3 different types of commands and between the commands inside each category. If an “EPP test” result is undefined/unanswered, the EPP service will be considered as unavailable from that probe until it is time to make a new test.

  • Measuring DNS parameters Every minute, every DNS probe will make an UDP or TCP “DNS test” to each of the public-­‐DNS registered “IP addresses” of the name servers of the domain name being monitored. If a “DNS test” result is undefined/unanswered, the tested IP will be considered unavailable from that probe until it is time to make a new test.

  • Parameters In calculating the MtM Exposure for each Transaction, the following parameters are set on the Transaction Date: ▪ On-Peak Initial Xxxx Xxxxx ▪ Off-Peak/On-Peak Price Ratio ▪ Off-Peak Initial Xxxx Xxxxx ▪ MW-Measure: initial Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Off-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Number of awarded Tranches In calculating the MtM Exposure for each Transaction, the following parameters are set each Trading Day subsequent to the Transaction Date: ▪ On-Peak Forward Price ▪ Off-Peak Forward Price ▪ Current Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity ▪ Off-Peak Estimated Energy Quantity Process to Update the On-Peak Initial Mark Prices and Off-Peak Initial Mark Prices on a Daily Basis On each Trading Day subsequent to the Transaction Date, the Pricing Agent will contact four Reference Market-Makers to obtain price quotes for on-peak and off-peak energy for PJM Western Hub. The Pricing Agent may not rely upon quotes from Seller or any Affiliate of Seller. The updated mark for a month will be equal to the average mark for that month over all sources from which a quote is available. If a monthly quote is available from any source, only the monthly quote or monthly quotes shall be used. Where quotes provide a bid and ask, the average shall be used. Where a quote for an individual month is unavailable, but the month is quoted as part of a “packaged” quote (e.g., January 2011 is only available in the form of a January/February 2011 “packaged” quote or an annual quote): ▪ If the other month/months of the package quote is/are also unavailable, then the marks for all months of the package will be calculated by multiplying the packaged quote by the ratio of the corresponding month to the corresponding calculated package quote from the previous day. Example: There are no On-Peak quotes available on day X during the contract for July 2011 or August 2011. However, there is an On-Peak July/August 2011 packaged quote of $73.00/MWh available. The On-Peak marks from day X-1 for July 2011 and August 2011 were $73.50/MWh and $76.50/MWh respectively. The day X On-Peak mark for July 2011 is set at 73.00 * [73.50] / [( (73.50 * 352) + (76.50 * 336) ) / (352+336) ] = 73 * (73.50/ 74.97) = $71.57/MWh. The day X On-Peak mark for August 2011 is set at 73.00 * [76.50] / [( (73.50 * 352) + (76.50*336) ) / (352+336) ] = 73 * (76.50 / 74.97) = $74.49/MWh. ▪ If the other month/months of the package quote is/are available, then the mark for the month will be set such that the average of the month and the other month(s) (weighted for either the On-Peak Hours or Off-Peak Hours as applicable) equals the packaged quote (see calculation example below).

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

Time is Money Join Law Insider Premium to draft better contracts faster.