I am trying to simulate a three phase node with a solar object for location in Sydney Australia.
I am using a CSV reader for climate data and an area of 6.1m^2 (1 kW) for the solar object.
Using a recorder i am recording hourly values for measured_real_power at the node.
I am not sure if the problem is with the model or the CSV reader but i am encoutering the following problems:
WARNING:Southern hemisphere solar position model may have issues
I am not sure what kindof issues and how to fix them.
The maximum output for measured_real_power for a year is 9.2kW when there is 0 load on the node specified, which seems too high for a 1 kw system area?
The recorder object output is almost one day after the start time of the simulation?
If i were to use a player object to update load values how would a specify that given that i have a three phase yearly load data?
The primary cause of your model woes appears to be units. Unfortunately, the csv_reader object expects to read things in at the default climate object units. For insolation values, this is unfortunately in W/ft^2. It looks like your values are in W/m^2 (so 1001 W/m^2 is roughly 93 W/ft^2). Therefore, your solar array is receiving about 10x as much energy as it should, hence the ~10x value that you are seeing. If you convert these to W/ft^2, your results will probably look better.
As I was looking at your files, I also noticed a couple other things. They aren't related to your issue, but I wanted to mention them:
First off, you need to arrange the clock section of your file a little. If you don't put the timezone variable first, GridLAB-D starts doing some very odd things (like running this in Eastern Standard Time and failing).
Secondly, the CSV file you posted seems to have been formatted funny. Assuming your version has the commas and everything it needs, I also noticed there is a negative solar_dir and solar_diff term. While it isn't causing the issues you see, there's just something that bugs me about a solar panel emitting direct and diffuse solar radiation -- it's supposed to absorb it!
-Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply, I fixed the issues with the CSV and results look better.
Is it possible to use a player object to update load values at the node, how would I specify that given that i have a three phase hourly load data for a year?
Can i use this command with a player, how would i specify the phase loads.
I am trying to simulate a three phase node with a solar object for location in Sydney Australia.
I am using a CSV reader for climate data and an area of 6.1m^2 (1 kW) for the solar object.
Using a recorder i am recording hourly values for measured_real_power at the node.
I am not sure if the problem is with the model or the CSV reader but i am encoutering the following problems:
WARNING:Southern hemisphere solar position model may have issues
I am not sure what kindof issues and how to fix them.
The maximum output for measured_real_power for a year is 9.2kW when there is 0 load on the node specified, which seems too high for a 1 kw system area?
The recorder object output is almost one day after the start time of the simulation?
If i were to use a player object to update load values how would a specify that given that i have a three phase yearly load data?
GLM code and CSV snippet below.
thanks,
GLM
This is how the CSV file looks likes
Hello Isfand,
The primary cause of your model woes appears to be units. Unfortunately, the csv_reader object expects to read things in at the default climate object units. For insolation values, this is unfortunately in W/ft^2. It looks like your values are in W/m^2 (so 1001 W/m^2 is roughly 93 W/ft^2). Therefore, your solar array is receiving about 10x as much energy as it should, hence the ~10x value that you are seeing. If you convert these to W/ft^2, your results will probably look better.
As I was looking at your files, I also noticed a couple other things. They aren't related to your issue, but I wanted to mention them:
First off, you need to arrange the clock section of your file a little. If you don't put the timezone variable first, GridLAB-D starts doing some very odd things (like running this in Eastern Standard Time and failing).
Secondly, the CSV file you posted seems to have been formatted funny. Assuming your version has the commas and everything it needs, I also noticed there is a negative solar_dir and solar_diff term. While it isn't causing the issues you see, there's just something that bugs me about a solar panel emitting direct and diffuse solar radiation -- it's supposed to absorb it!
-Frank
Hi Frank,
Thanks for the reply, I fixed the issues with the CSV and results look better.
Is it possible to use a player object to update load values at the node, how would I specify that given that i have a three phase hourly load data for a year?
Can i use this command with a player, how would i specify the phase loads.
object load {
phases "ABCD";
name LOAD_1;
parent NL1;
constant_power_A X;
constant_power_B X;
constant_power_C X;
nominal_voltage 433;
}
thanks,
Player objects can push values to any (input) parameter in GridLAB-D. For a constant_power value, this would just be:
and the player would just use standard formatting. Please see:
http://gridlab-d.sourceforge.net/wiki/index.php/Player
http://gridlab-d.sourceforge.net/wiki/index.php/Class_schedule