Revision history [back]

I have a fair amount of Measures each with several measure options, and therefore do not wish to create the various design alternatives by hand as it would be too tedious. I wish to compute the different permutations based on some inner logic like "Measure A" and "Measure B" are actually alternatives for the same Energy Efficiency Measure (EEM) so they should be treated as such.

Now that PAT 2.x has be revamped and seems to use a JSON format, can I script it? I guess I need to modify pat.json, but I'm wondering if I can specifically use OpenStudio's API for this or if I need to just treat the JSON file like any other?

I have a fair amount of Measures each with several measure options, and therefore do not wish to create the various design alternatives by hand as it would be too tedious. I wish to compute the different permutations based on some inner logic like "Measure A" and "Measure B" are actually alternatives for the same Energy Efficiency Measure (EEM) so they should be treated as such.

Now that PAT 2.x has be revamped and seems to use a JSON format, can I script it? I guess I need to modify pat.json, but I'm wondering if I can specifically use OpenStudio's API for this or if I need to just treat the JSON file like any other?

I have a fair amount of Measures each with several measure options, and therefore do not wish to create the various design alternatives by hand as it would be too tedious. I wish to compute the different permutations based on some inner logic like "Measure A" and "Measure B" are actually alternatives for the same Energy Efficiency Measure (EEM) so they should be treated as such.

Now that PAT 2.x has be revamped and seems to use a JSON format, can I script it? I guess I need to modify pat.json, but I'm wondering if I can specifically use OpenStudio's API for this or if I need to just treat the JSON file like any other?

If I have to change the JSON itself, how can I set some parameters such as $$hashKey for designAlternatives etc.?

I have a fair amount of Measures each with several measure options, and therefore do not wish to create the various design alternatives by hand as it would be too tedious. I wish to compute the different permutations based on some inner logic like "Measure A" and "Measure B" are actually alternatives for the same Energy Efficiency Measure (EEM) so they should be treated as such.

Now that PAT 2.x has be revamped and seems to use a JSON format, can I script it? I guess I need to modify pat.json, but I'm wondering if I can specifically use OpenStudio's API for this or if I need to just treat the JSON file like any other?

If I have to change the JSON itself, how can I set some parameters such as $$hashKey for designAlternatives etc.?