Describe the bug
When PVsyst OND - PAN to SAM macro imports module data from a PAN file, it only recognizes the "mtSiMono" value of the "technol" parameter, so SAM assigns the mono-Silicon module type to all modules. This is not really a problem for the model because that parameter is not used in simulation calculations, but it makes it appear that something is wrong with how SAM is interpreting the data in the PAN file.
See Line 136 in the macro: https://github.com/NREL/SAM/blob/c8ef80585337bebce4753f6d2f654ba3226b4b1b/deploy/runtime/macros/Flat%20Plate%20PV/PVsyst%20OND%20-%20PAN%20to%20SAM.lk#L136
We now have a list of valid values of technol that we can use to update the macro. These may change over time, so it is possible that in the future, the value of technol in a PAN file may not be in the list, so the macro should be designed to handle that possibility.
I have sample PAN files for testing and the list of variable values, but am not sure they are public information, so will not post them here.
Describe the bug
When PVsyst OND - PAN to SAM macro imports module data from a PAN file, it only recognizes the "mtSiMono" value of the "technol" parameter, so SAM assigns the mono-Silicon module type to all modules. This is not really a problem for the model because that parameter is not used in simulation calculations, but it makes it appear that something is wrong with how SAM is interpreting the data in the PAN file.
See Line 136 in the macro: https://github.com/NREL/SAM/blob/c8ef80585337bebce4753f6d2f654ba3226b4b1b/deploy/runtime/macros/Flat%20Plate%20PV/PVsyst%20OND%20-%20PAN%20to%20SAM.lk#L136
We now have a list of valid values of technol that we can use to update the macro. These may change over time, so it is possible that in the future, the value of technol in a PAN file may not be in the list, so the macro should be designed to handle that possibility.
I have sample PAN files for testing and the list of variable values, but am not sure they are public information, so will not post them here.