Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Add “is it true tracking” Boolean output to singleaxis

Aberta
  • Algo errado?
#2,672 20 comentários 2 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

  • #2709 de @r0hansaxena — fechado sem integrar

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
python
Domínio
backend

Direção de pesquisa

Start with singleaxis in pvlib/tracking.py, where the backtracking calculation determines the tracker rotation. Read the closed, unmerged PR #2709 and the linked Google group thread first to learn why it was not merged and what output shape was discussed. Done means singleaxis can return a boolean series marking backtracking periods, with tests in pvlib/tests/test_tracking.py covering both modes.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement

Is your feature request related to a problem? Please describe.
It would be nice to be able to easily identify periods where trackers are in backtracking mode vs regular (true) tracking mode.

Describe the solution you'd like
A Boolean timeseries output from the singleaxis function.

Describe alternatives you've considered
One option is running singleaxis twice, with and without backtracking, and looking for differences. Or comparing with idea angle from shading.projected_solar_zenith_angle.

Additional context
This would be helpful when, e.g., setting tracker position error thresholds/tolerances that depend on tracking mode, where error in the direction of not causing self shade is more tolerable than error in the direction of causing shade.

Related, it would also be helpful to be able to differentiate AM vs PM backtracking, for similar reasons. That may be too much to add here, though. [edit: as Adam pointed out below, AM vs PM can easily be inferred from rotation angle.]

See this Google group thread for some discussion: https://groups.google.com/d/msgid/pvlib-python/ea0e5e62-6cd5-4a7c-bf7d-08c625fa51c6n%40googlegroups.com?utm_medium=email&utm_source=footer

Linguagem predominante
Python
Estrelas
1.7k
Forks
1.2k
Merge médio
3d 18h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pvlib/pvlib-python

Todas as issues de pvlib/pvlib-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.