Skip to content

Conversation

@mjprilliman
Copy link
Collaborator

-New terrain tilt angle and terrain azimuth (measured East of North) inputs for subarrays
-Only enabled for 1-axis tracking for this release
-If backtracking enabled, backtracking angle influenced by terrain inputs
-If linear shading is enabled, shadeFraction accounts for terrain input effects on beam self-shading
-Reference: https://www.nrel.gov/docs/fy20osti/76626.pdf

@mjprilliman mjprilliman added new feature pv pvsam1, pvwatts, hcpv labels Nov 9, 2021
@mjprilliman mjprilliman added this to the SAM Fall 2021 Release milestone Nov 9, 2021
@mjprilliman mjprilliman self-assigned this Nov 9, 2021
@mjprilliman
Copy link
Collaborator Author

@cpaulgilman
Copy link
Collaborator

@mjprilliman For which of the following conditions do the terrain slope inputs have an effect on results?

  1. Self shading disabled
  2. Self shading enabled with linear option
  3. Self shading enabled with non-linear option

@mjprilliman
Copy link
Collaborator Author

@mjprilliman For which of the following conditions do the terrain slope inputs have an effect on results?

  1. Self shading disabled
  2. Self shading enabled with linear option
  3. Self shading enabled with non-linear option
  1. Only affects results if backtracking is enabled (angle changes to account for slope)
  2. Affects results through linear beam portion of self-shading (shadeFraction), can also vary results through backtracking if enabled (eliminates self-shading)
  3. Only affects results with backtracking enabled (angle changes to account for slope), which would theoretically eliminate self-shading

@cpaulgilman
Copy link
Collaborator

This implementation is probably fine for now.

For future improvements:

  • Consider enabling slope inputs for combinations that have no effect. For example, disable when self shading is enabled but backtracking is disabled.
  • Consider moving to "Shading and Layout" page.

Copy link
Collaborator

@janinefreeman janinefreeman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with Paul's comments- Matt, can you make issues for those future improvements and assign to patch 1 for now? Thanks!

@mjprilliman mjprilliman merged commit eb32770 into develop Nov 12, 2021
@mjprilliman mjprilliman deleted the cross_axis_slope branch November 12, 2021 18:09
@cpaulgilman cpaulgilman added the added to release notes PR and/or issue has been added to release notes for a public release label Dec 2, 2021
cpaulgilman added a commit that referenced this pull request Feb 17, 2022
Revise description of load data time convention.

Remove O&M cost content from Installation Costs topics.

Add ETES topics and fix broken help links.

Fix typo on battery storage FOM "BTM" insteasd of "FOM"

Wind resource files can now be .csv in addition to .srw

Revise capacity factor descriptions for PV and Battery storage configs, #905

Wave resource instructions for converting from time series to JPD, #892

Revise PV land area calculations to account for GCR and tilt angle, #928

Add pvlib column headings to SAM CSV format description, NREL/ssc#754

Revised Operating Cost input pages

Check for "annual energy" vs new "electricity to grid".

Change "battery autonomy" to "autonomy".

Revise power tower heliostat field to better explain how check box vs button works.

Add note for degradation by year that Year 1 value should be zero, #755

Remove debt from payback period description. Also remove detailed cash flow descriptions and replace with mention of send-to-Excel with equations and spreadsheets on website. See Amir Nashed email 1/19/21 and https://sam.nrel.gov/forum/forum-general/1052

Revise Electricity Purchases page to be specific for FOM projects

New LCOS metrics: #529

Electricity rates revisions from Brian.

Reporting of electricity bill in time series results, see NREL/ssc#652

New parametrics features

Parametrics description of how to work with SchedNumeric variables like PPA price. See Brian email 7/21/2021

Update Heliostat Field per #717

New PV slope inputs on System Design page. See #742, NREL/ssc#648

New "Limit debt fraction" Input on Financial Parameters page for PPA models

New ETES model.

Fix outdated description of NSRDB in Location and Resource topic

UDPC updates from Ty, see Revisions 2021 folder. Also post new PDF version of Ty and Matt's description under "CSP Power Cycle Models"  on SAM website https://sam.nrel.gov/concentrating-solar-power/csp-publications.html,  https://sam.nrel.gov/images/web_page_files/Neises-DRAFT-user-defined-power-cycle-v3-2018.pdf

Fix excess generation descriptions in help: https://sam.nrel.gov/forum/forum-general/3485. Also maybe change "Excess generation" to "Excess generation for net metering" or similar.

Note for URDB download that demand ratchet data in URDB is unreliable, so check with data sheet.

Demand charges with ratcheting lookback months. See Revision Notes mirletz-RE Adding billing demand lookback to SAM.msg, see [[F:\OneDrive\SAM\Utility Rates\Demand Ratchets\Initial Tests May 2021]]

Update pv smoothing per Steve's email 12/9/2021 "pv smoothing question"

Improve description of FOM automated dispatch. See https://sam.nrel.gov/forum/forum-general/3681

Revise electricity rates page

Consolidate weekday/weekend schedule descriptions.

SWH remove old hot water draw import instructions.

Revise electricity purchases PPA price option not available with Specify IRR target, and purchases treated as tax-deductible operating expense.

Move electricity purchases page to from Battery section to Electricity Rates and Load section

Edit Lifetime Data add note about pasting data from Excel: Thousands comma separator causes paste not to work correctly, e.g, 1,000 is pasted as 1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

added to release notes PR and/or issue has been added to release notes for a public release new feature pv pvsam1, pvwatts, hcpv

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants