ERROR: No availability_derate_cap_rule function in subtype module gridpath.project.availability

[krish08jack]

ERROR: No availability_derate_cap_rule function in subtype module gridpath.project.availability

• Could you please confirm:
• Whether availability_derate_cap_rule was moved, renamed, or deprecated in recent commits?
• If a new availability subtype needs to be specified in the project inputs?
• Any recent updates to the availability.py structure that may require manual edits?

ERROR:root:ERROR! No availability_derate_cap_rule function in subtype module <module 'gridpath.project.availability' from 'c:\gridpath\gridpath-develop_new\gridpath-develop\gridpath\project\availability\init.py'>.
error_cep.txt

[anamileva]

This error arises when an availability type is missing for one or more of the projects in the case.

As of v2025.7.0, availability types are no longer required as an input (they will default to "exogenous").

[krish08jack]

This error arises when an availability type is missing for one or more of the projects in the case.

As of v2025.7.0, availability types are no longer required as an input (they will default to "exogenous").

Hi Anamileva
Thanks for the response
Enclosing the project_availability_type file, which lists all projects along with their corresponding availability classifications.

1. The project_availability_type file lists a total of 72 projects, of which 63CSV files are included in the project_availability_exogenous folder.
2. The remaining projects are considered future or upcoming plants, as they are being accounted for in the Capacity Expansion Model
   Referring to point 1 , Projects assigned a value of 1 under the column C -exogenous_availability_scenario_id and the same are categorized as project_availability_exogenous.

I am using gripath version = "v0.16.1"
Still error is persistance.
Thanks
2_project_availability_types.csv