<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/electricdss/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/electricdss/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/electricdss/discussion/</id><updated>2026-11-17T00:48:16.629000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>IEEE 33 bus </title><link href="https://sourceforge.net/p/electricdss/discussion/861976/thread/1608f0f43d/?limit=25#d1a0" rel="alternate"/><published>2026-11-17T00:48:16.629000Z</published><updated>2026-11-17T00:48:16.629000Z</updated><author><name>Rai Jayde</name><uri>https://sourceforge.net/u/raijayde/</uri></author><id>https://sourceforge.netbf36ad3858b5f83415902993ad4407b84c0de589</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello, do you have the update code for IEEE 33-bus&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Data for Texas System</title><link href="https://sourceforge.net/p/electricdss/discussion/861976/thread/cdd34472dd/?limit=100#7a12" rel="alternate"/><published>2026-10-13T22:39:18.326000Z</published><updated>2026-10-13T22:39:18.326000Z</updated><author><name>Paulo Meira</name><uri>https://sourceforge.net/u/meira/</uri></author><id>https://sourceforge.net0f777da5e3c9eb0d836cff606f3b0996aa850bd0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;They seem to follow the expected location from the relative path in the DSS scripts, i.e., &lt;a href="https://data.openei.org/s3_viewer?bucket=oedi-data-lake&amp;amp;prefix=SMART-DS%2Fv0.9%2F2016%2FFull_Texas%2Fprofiles%2F" rel="nofollow"&gt;https://data.openei.org/s3_viewer?bucket=oedi-data-lake&amp;amp;prefix=SMART-DS%2Fv0.9%2F2016%2FFull_Texas%2Fprofiles%2F&lt;/a&gt; from your sample.&lt;/p&gt;
&lt;p&gt;You probably can get more info from the repo at &lt;a href="https://github.com/openEDI/documentation/blob/main/SMART-DS/Readme.md" rel="nofollow"&gt;https://github.com/openEDI/documentation/blob/main/SMART-DS/Readme.md&lt;/a&gt; (it's unlikely the authors subscribe to this forum).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Data for Texas System</title><link href="https://sourceforge.net/p/electricdss/discussion/861976/thread/cdd34472dd/?limit=25#7134" rel="alternate"/><published>2026-10-11T05:34:37.165000Z</published><updated>2026-10-11T05:34:37.165000Z</updated><author><name>Mahdi Kazemi Razi </name><uri>https://sourceforge.net/u/mehdi1995/</uri></author><id>https://sourceforge.net665a6fa89a4ad8ccd0408b9ded8083f22218b6dd</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am trying to use a network for Texas that is defined in OpenDSS. The network is available at &lt;a href="https://data.openei.org/s3_viewer?bucket=oedi-data-lake&amp;amp;prefix=SMART-DS%2Fv0.9%2F." rel="nofollow"&gt;https://data.openei.org/s3_viewer?bucket=oedi-data-lake&amp;amp;prefix=SMART-DS%2Fv0.9%2F.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Inside the loadshape.dss, it needs some files that are defined by file=../../../../../profiles/res_kw_4691_pu.csv. Could you please where at this aws address, I can find this csv files? All the files for load data at &lt;a href="https://data.openei.org/s3_viewer?bucket=oedi-data-lake&amp;amp;prefix=SMART-DS%2Fv0.9%2F2016%2FFull_Texas%2Fload_data%2F&amp;amp;limit=50" rel="nofollow"&gt;https://data.openei.org/s3_viewer?bucket=oedi-data-lake&amp;amp;prefix=SMART-DS%2Fv0.9%2F2016%2FFull_Texas%2Fload_data%2F&amp;amp;limit=50&lt;/a&gt; are in parquet format.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>OpenDSS Visualizer</title><link href="https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#6d4b" rel="alternate"/><published>2026-09-04T03:01:22.478000Z</published><updated>2026-09-04T03:01:22.478000Z</updated><author><name>Meisam Ansari</name><uri>https://sourceforge.net/u/ansri273/</uri></author><id>https://sourceforge.net0cb3ed0047e48579d6e8c35ec2c44703f8894208</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There are many utilities and consulting companies that have started leveraging OpenDSS in some of their batch analysis where conventional enterprise tools like CYME, Synergi, Windmill, etc do not easily support them. The gap is that the models must first be converted from the current tools to OpenDSS and thoroughly validated. An advanced power system engineer who has worked with OpenDSS and has coding skills can most likely write a small pipeline and try to do it. However, many engineers do not have this skill, so although some efforts, like creating a useful UI on top of opendss seems redundant but still have value in some directions. Especially if the tool is developed on cloude infrastructure and can be easily used and scaled. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>OpenDSS Visualizer</title><link href="https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#129b" rel="alternate"/><published>2026-09-04T03:01:21.830000Z</published><updated>2026-09-04T03:01:21.830000Z</updated><author><name>Meisam Ansari</name><uri>https://sourceforge.net/u/ansri273/</uri></author><id>https://sourceforge.net782d855ded3783bacb866709968bcdf659c117a2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There are many utilities and consulting companies that have started leveraging OpenDSS in some of their batch analysis where conventional enterprise tools like CYME, Synergi, Windmill, etc do not easily support them. The gap is that the models must first be converted from the current tools to OpenDSS and thoroughly validated. An advanced power system engineer who has worked with OpenDSS and has coding skills can most likely write a small pipeline and try to do it. However, many engineers do not have this skill, so although some efforts, like creating a useful UI on top of opendss seems redundant but still have value in some directions. Especially if the tool is developed on cloude infrastructure and can be easily used and scaled. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Mathematical Method</title><link href="https://sourceforge.net/p/electricdss/discussion/861977/thread/7473cb25/?limit=25#e27f" rel="alternate"/><published>2026-09-03T16:27:06.786000Z</published><updated>2026-09-03T16:27:06.786000Z</updated><author><name>Hamza</name><uri>https://sourceforge.net/u/davednick/</uri></author><id>https://sourceforge.net80fae0d4aaa96c4299e21e83c07755f304708708</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The explanation of the iterative process is really helpful, especially the distinction between the snapshot and direct modes. For anyone working through the math behind a problem, I also find it useful to verify the basic calculations step by step with an online math calculator such as La &lt;a href="https://lacalculadora-dealicia.com/" rel="nofollow"&gt;Calculadora de Alicia&lt;/a&gt; before comparing the results with OpenDSS. It makes it easier to spot a simple arithmetic mistake before looking for a problem in the simulation.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Struggling to get GFM Storage to sustain output past 1 timestep (IEEE 13-bus)</title><link href="https://sourceforge.net/p/electricdss/discussion/861977/thread/29187f3275/?limit=25#b23c" rel="alternate"/><published>2026-08-24T19:42:46.737000Z</published><updated>2026-08-24T19:42:46.737000Z</updated><author><name>Sergio Miguel</name><uri>https://sourceforge.net/u/sergio-ferro/</uri></author><id>https://sourceforge.net6dd20b2f48b79abb236776988421c27a2111ed34</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thank you so much for the help, it really cleared up my doubt. Sorry for the delayed reply here on the forum. I really appreciate the suggested material as well, and I'll be sure to come back to the forum if anything else comes up.&lt;/p&gt;
&lt;p&gt;Thanks again!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>OpenDSS Visualizer</title><link href="https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#2428/48fa/ae0f/2d71/65d6/1e0d" rel="alternate"/><published>2026-08-24T14:50:39.390000Z</published><updated>2026-08-24T14:50:39.390000Z</updated><author><name>Davis Montenegro</name><uri>https://sourceforge.net/u/davismont/</uri></author><id>https://sourceforge.net107554d27fd80ed8b4709ec81d063402b0ac8290</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Thanks for sharing this. My initial thought is that this could be a useful opportunity in the right context. Traversing the circuit model and retrieving element properties can already be done quite efficiently today, either through the circuit tree or by using the incidence and Laplacian matrices that DSS already generates. With those structures in place, the kinds of actions you described above should be fairly straightforward. They also help avoid creating unnecessary duplicates.&lt;br/&gt;
I would be especially interested in something like inference, although that would likely require incomplete datasets or models, along with more diverse data sources beyond the DSS model itself. That, in my view, would make for a more compelling case. The other items seem more foundational and are already considered within the program, as well as accessible through the available interfaces.&lt;/p&gt;
&lt;p&gt;Best,&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Tutorial</title><link href="https://sourceforge.net/p/electricdss/discussion/beginners/thread/997b3515b0/?limit=25#31da/a856" rel="alternate"/><published>2026-08-20T12:32:21.039000Z</published><updated>2026-08-20T12:32:21.039000Z</updated><author><name>Davis Montenegro</name><uri>https://sourceforge.net/u/davismont/</uri></author><id>https://sourceforge.nete2f437f01de97f9f9cbeb30fa90a584ed718515a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There are plenty of resources available, including this forum, and folks here are always happy to help. Typically, we use this space to work through specific questions about the software, like “How do I do this?” or “Why isn’t this working the way I expect?”&lt;br/&gt;
Do you have a particular application or use case in mind? &lt;/p&gt;
&lt;p&gt;Best,&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>OpenDSS Visualizer</title><link href="https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#2428/48fa/ae0f" rel="alternate"/><published>2026-08-20T12:29:04.251000Z</published><updated>2026-08-20T12:29:04.251000Z</updated><author><name>Davis Montenegro</name><uri>https://sourceforge.net/u/davismont/</uri></author><id>https://sourceforge.netfeaa50ce55c443698afb474a46306dfa8a7548ec</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Thanks for sharing this, it helps me understand the direction you’re taking. From what you described, it sounds like you’re trying to combine an ontology layer with a DSS‑based knowledge graph, is that right? If so, I’m curious how this approach differs from simply exporting the circuit’s CIM dataset from DSS and then loading it into a knowledge graph using Python tools like rdflib. Is that essentially what you’re doing now, or is your workflow meaningfully different?&lt;/p&gt;
&lt;p&gt;Best,&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>