Jump to content

Error "Info: parameter Pitch was set, Warning: parameter Pitch did not change, The GCR used for the backtracking algorithm (0.675) differs from ..."


Recommended Posts

Posted

I am attempting to run batch simulations where the pitch is varied (screenshots are attached).

The tracker pitch in the shading scene is 3m. The following error is being displayed for runs where the simulated pitch differs from 3m:

"Info: parameter Pitch was set, Warning: parameter Pitch did not change, The GCR used for the backtracking algorithm (0.675) differs from the average GCR (0.289)."

The following error is being displayed for runs where the simulated pitch is 3m:

"Warning: parameter Pitch did not change"

I ran some tests in batch mode and in single simulation mode and a quick comparison indicated the results were the same i.e. the error messages returned when running in batch mode are bogus. Is anyone able to confirm that the error messages are bogus?

arrays.png

batch_params.png

batch_settings.png

  • 2 weeks later...
Posted

You still have the column "Pitch" in your batch file. Since there are only trackers in the scene, the pitch cannot be changed, which triggers the warning. What matters is the other column, "Trackers pitch EW". I would recommend removing the "Pitch column" and rerunning the batch.

Note also that you should be mindful of how the backtracking parameters were set (3D scene > Tools > Backtracking management):
image.png.52556dac392e785b98ecf8aa024abc13.png

Here the mode is manual (automatic unchecked). This means that if the batch mode changes the pitch, the backtracking algorithm will not follow, and the yield may decrease (either from being suboptimally oriented or from shadings).

Instead if you choose "Automatic", then the backtracking will adapt to the changes from the batch.

image.png.22606d21e2f4caeff9e2da932c67b3d8.png

 


 

Posted

Hi Michelle. Thank you for the response. Removing the Pitch column did remove the first error ("Warning: parameter Pitch did not change") but the second error ("The GCR used for the backtracking algorithm (0.675) differs from the average GCR (0.289)") remains. Below I will provide a minimum reproducible example to illustrate the error.

    1. Open _DEMO_COMMERCIAL.PRJ
    2. Click on Orientation and change to 'Tracking, horizontal axis N-S' and enable Backtracking. Click OK.
    3. image.png.5f91359488940609459f5f05b54c9962.png
    1. Click on Near Shadings, then on Construction/Perspective. Then Create/Array of Trackers
    2. image.thumb.png.a484d883c1e76f81ac48bcdacf1f4982.png
    3. Default array of four trackers appears. Make no changes. Close Object.
    4. Click on Tools/Backtracking management. Verify that "Automatic" is checked
    5. image.png.fe13eefde522b445bafeb6c0a797a01f.png
    6. Compute shading factor table.
    7. Click OK to exit Near Shadings.
    8. Click on Advanced Simulation, then Batch simulation.
    9. Select to vary only "Pitch E-W between trackers"
    10. image.png.fd11c61df88a17565f8632c3f96175a1.png
    11. Under the "Batch CSV Files" tab, select "New file" and then click OK to close the window.
    12. Open the BatchParams file, which looks like this:
    13. image.png.00da540da0fec9136a200840a659e36f.png
    14. Modify it to schedule a batch simulation for three scenarios with varying tracker pitch:
    15. image.png.da4965eb8038eab14ba80ca98b6c4167.png
    16. Click "Simulation" to run
    17. image.png.bc30744fdaa0ce2add8834a89184b355.png
    18. Inspecting the results, we see the error message is returned for  cases where the tracker pitch varies from the tracker pitch in the 3D drawing in Near Shadings
    19. image.thumb.png.2405132cd6d94b8d409ed62240c6d7bc.png

 

It seems the tracker pitch is changing each simulation but the GCR used for backtracking is not.

 

Do you know what I'm missing?

Posted

I have checked further, and the pitch seems to be effectively changed, even for the backtracking algorithm. This is despite the message saying otherwise. The message seems to stem from a check, before updating the backtracking algorithm. It is therefore not relevant.

Note that this does not happen in version 8 anymore, in principle. Have you checked ?

Posted

Correct, I do not see these error messages with v8.0.1 (all of the above was done with v7.4.8). Thank you for your help, Michele!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...