- Posts: 11
The SDK tool for Mac OSX has not been updated to reflect ssc capabilities
- caseyzak24
- Topic Author
Less
More
30 Jan 2019 17:20 #6630
by caseyzak24
The SDK tool for Mac OSX has not been updated to reflect ssc capabilities was created by caseyzak24
I've used the SDK tool in Windows and it reflects changes that went into the latest version of the ssc (e.g. the definition of subarray_x_poa_eff is the poa after IAM effects). However, I just downloaded the SDKtool for Mac and it looks unchanged from the previous version (e.g. subarray_x_poa_eff is the poa after shading and soiling). Any idea when this can be fixed?
I am happy to post this on the github page as well if that would be helpful
I am happy to post this on the github page as well if that would be helpful
Please Log in or Create an account to join the conversation.
- pgilman
Less
More
- Posts: 5447
01 Feb 2019 17:56 #6631
by pgilman
Replied by pgilman on topic The SDK tool for Mac OSX has not been updated to reflect ssc capabilities
Dear Casey,
The SDKtool interacts which whatever version of the ssc library you load. You can use the "Load/unload library" and "Choose SSC library" buttons in the Module Browser to choose a different library.
To load the current library in SDKtook for macOS, open a Finder window, and control-click the SAM app icon to show the package contents, and copy /Contents/Frameworks/ssc.dylib to the Desktop or some other folder you have access to. Then start SDKtool, and in the Module Browser, click Choose SSC library and open the ssc.dylib file.
As you may already know, as of SAM 2018.11.11, the SDKtool now comes with the SAM desktop software. We did that with the intention of making it easier to keep code you generate from SAM consistent with the SSC library you explore in SDKtool. If you have more than one version of SAM installed on your computer, or copies of different SSC libraries, you can load those libraries in SDKtool -- for example, using SDKtool that comes with SAM 2018.11.11, you can load the SSC library from a SAM 2017.9.5 installation, or a copy of an even older SSC library version 174. The new instructions on the SDK page provides some additional explanation: sam.nrel.gov/sdk .
Best regards,
Paul.
The SDKtool interacts which whatever version of the ssc library you load. You can use the "Load/unload library" and "Choose SSC library" buttons in the Module Browser to choose a different library.
To load the current library in SDKtook for macOS, open a Finder window, and control-click the SAM app icon to show the package contents, and copy /Contents/Frameworks/ssc.dylib to the Desktop or some other folder you have access to. Then start SDKtool, and in the Module Browser, click Choose SSC library and open the ssc.dylib file.
As you may already know, as of SAM 2018.11.11, the SDKtool now comes with the SAM desktop software. We did that with the intention of making it easier to keep code you generate from SAM consistent with the SSC library you explore in SDKtool. If you have more than one version of SAM installed on your computer, or copies of different SSC libraries, you can load those libraries in SDKtool -- for example, using SDKtool that comes with SAM 2018.11.11, you can load the SSC library from a SAM 2017.9.5 installation, or a copy of an even older SSC library version 174. The new instructions on the SDK page provides some additional explanation: sam.nrel.gov/sdk .
Best regards,
Paul.
Please Log in or Create an account to join the conversation.
- pgilman
Less
More
- Posts: 5447
01 Feb 2019 17:57 #6632
by pgilman
Replied by pgilman on topic The SDK tool for Mac OSX has not been updated to reflect ssc capabilities
Dear Casey,
The SDKtool interacts which whatever version of the ssc library you load. You can use the "Load/unload library" and "Choose SSC library" buttons in the Module Browser to choose a different library.
To load the current library in SDKtook for macOS, open a Finder window, and control-click the SAM app icon to show the package contents, and copy /Contents/Frameworks/ssc.dylib to the Desktop or some other folder you have access to. Then start SDKtool, and in the Module Browser, click Choose SSC library and open the ssc.dylib file.
As you may already know, as of SAM 2018.11.11, the SDKtool now comes with the SAM desktop software. We did that with the intention of making it easier to keep code you generate from SAM consistent with the SSC library you explore in SDKtool. If you have more than one version of SAM installed on your computer, or copies of different SSC libraries, you can load those libraries in SDKtool -- for example, using SDKtool that comes with SAM 2018.11.11, you could load the SSC library from a SAM 2017.9.5 installation, or you could a copy of an even older SSC library like version 174 that came in the SDK zip files for older versions. The new instructions on the SDK page provides some additional explanation: sam.nrel.gov/sdk .
Best regards,
Paul.
The SDKtool interacts which whatever version of the ssc library you load. You can use the "Load/unload library" and "Choose SSC library" buttons in the Module Browser to choose a different library.
To load the current library in SDKtook for macOS, open a Finder window, and control-click the SAM app icon to show the package contents, and copy /Contents/Frameworks/ssc.dylib to the Desktop or some other folder you have access to. Then start SDKtool, and in the Module Browser, click Choose SSC library and open the ssc.dylib file.
As you may already know, as of SAM 2018.11.11, the SDKtool now comes with the SAM desktop software. We did that with the intention of making it easier to keep code you generate from SAM consistent with the SSC library you explore in SDKtool. If you have more than one version of SAM installed on your computer, or copies of different SSC libraries, you can load those libraries in SDKtool -- for example, using SDKtool that comes with SAM 2018.11.11, you could load the SSC library from a SAM 2017.9.5 installation, or you could a copy of an even older SSC library like version 174 that came in the SDK zip files for older versions. The new instructions on the SDK page provides some additional explanation: sam.nrel.gov/sdk .
Best regards,
Paul.
Please Log in or Create an account to join the conversation.
Moderators: pgilman