Jason Fuller

1 - That's how I would approach it, too. You might consider verifying that your conversions are correct (units always trip me up). Potentially you could use the OpenDSS export function, as it doesn't use sequence components in the calculation, but rather converts it to impedance values: https://sourceforge.net/p/electricdss/discussion/beginners/thread/008deb6d/ 2 - Again, that's how I would approach it, too. You put a new line (and source node) with an equivalent impedance. That kind of jump in losses...

MA / Frank, Maybe to add a little to this, as I'm pretty sure I hacked this code in for a project 6 or 7 years ago. To Frank's point, it has not been well tested, particularly around wider usage (i.e., access to some of the variables). For example, there is a coefficient of performance variable in the code: // @TODO: These values were created from HPWH project; need to make them more accessible HP_COP = (1.04 + (1.21 - 1.04) * (get_Tambient(location) - 50) / (70 - 50)) * (5.259 - 0.0255 * Tw); That...

MA / Frank, Maybe to add a little to this, as I'm pretty sure I hacked this code in for a project 6 or 7 years ago. To Frank's point, it has not been well tested, particularly around wider usage (i.e., access to some of the variables). For example, there is a coefficient of performance variable in the code: // @TODO: These values were created from HPWH project; need to make them more accessible HP_COP = (1.04 + (1.21 - 1.04) * (get_Tambient(location) - 50) / (70 - 50)) * (5.259 - 0.0255 * Tw); ~~~~...

duyanran, To correct your time issue: In the clock object, the timezone specification needs to come first (there are reasons for making this order dependent): clock { timestamp '2014-01-01 0:00:00'; starttime '2014-01-01 0:00:00'; stoptime '2014-01-07 0:01:30'; timezone EST+5EDT; } change to: clock { timezone EST+5EDT; timestamp '2014-01-01 0:00:00'; starttime '2014-01-01 0:00:00'; stoptime '2014-01-07 0:01:30'; } To use a meter to capture those values, you just need to replace the node object with...

NOTE: re-posted from https://github.com/gridlab-d/gridlab-d/issues/1252 i try to get current info from a IEEE-13 nodes file, but the timestamp just didnt match and the output record didnt follow with what i wish it to be, its a bit hard for me to describe it, so i post the relevant codes here. i am new to this software, really need some help， thanks！ //--------------- this is my clock info --------------------- clock { timestamp '2014-01-01 0:00:00'; starttime '2014-01-01 0:00:00'; stoptime '2014-01-07...

As of v4.1, load, DG, and other DER short circuit components are not considered. GLD is using a more classical method for calculating the short circuit current, where DERs are "disconnected" due to the relatively small scale of contribution. This is a feature that is being developed. The challenging part about this is what do you want the fault contribution to be and over what timescale? Depending on the age of the inverter, what generation of standards it is adhering to, etc., the answer changes....

The ratings are all default values and not calculated (1000 A and 2000 A respectively). It should just take in the values you provided and use them directly. We don't really do any modifications of those values because they don't typically impact the solution. Kishan - would you try adding: rating.summer.continuous 1200; rating.summer.emergency 1200; rating.winter.continuous 1200; rating.winter.emergency 1200; to your neutral overhead_line_conductor and run the model? I'm curious to see if the neutral...

Carlos, Did you adjust your lat/long in the CSV file (input into the CSV reader)? I'm not even sure if the csv reader will pick up a lat/long; we'll have to check on that one. Are you wanting to enter TMY2 or TMY3 directly (i.e., do you have a TMY3 data file, which the one above mostly looks like)? If so, you don't need to go through the CSV reader: object climate { name "Yakima"; tmyfile "../WA-Yakima.tmy3"; }