<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Project OpenDSS</title><link>https://sourceforge.net/p/electricdss/</link><description>Recent changes to Project OpenDSS</description><atom:link href="https://sourceforge.net/p/electricdss/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 17 Nov 2026 00:48:16 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/electricdss/feed.rss" rel="self" type="application/rss+xml"/><item><title>IEEE 33 bus </title><link>https://sourceforge.net/p/electricdss/discussion/861976/thread/1608f0f43d/?limit=25#d1a0</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rai Jayde</dc:creator><pubDate>Tue, 17 Nov 2026 00:48:16 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netbf36ad3858b5f83415902993ad4407b84c0de589</guid></item><item><title>Data for Texas System</title><link>https://sourceforge.net/p/electricdss/discussion/861976/thread/cdd34472dd/?limit=100#7a12</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paulo Meira</dc:creator><pubDate>Tue, 13 Oct 2026 22:39:18 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0f777da5e3c9eb0d836cff606f3b0996aa850bd0</guid></item><item><title>Data for Texas System</title><link>https://sourceforge.net/p/electricdss/discussion/861976/thread/cdd34472dd/?limit=25#7134</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mahdi Kazemi Razi </dc:creator><pubDate>Sun, 11 Oct 2026 05:34:37 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net665a6fa89a4ad8ccd0408b9ded8083f22218b6dd</guid></item><item><title>Adding unified interface for DLL generation in C++. This version is also compatible with MacOS, extending the compilation capabilities. Currently the DLL has been tested for compilation in Windows,...</title><link>https://sourceforge.net/p/electricdss/code/4176/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Adding unified interface for DLL generation in C++. This version is also compatible with MacOS, extending the compilation capabilities. Currently the DLL has been tested for compilation in Windows, Linux and MacOS.&lt;br/&gt;&lt;a href="/p/electricdss/code/4176/"&gt;View Changes&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">davismont</dc:creator><pubDate>Sat, 05 Sep 2026 12:09:55 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net/p/electricdss/code/4176/</guid></item><item><title>Adding unified interface to the DLL as alternative for exposing the code as infrastructure.</title><link>https://sourceforge.net/p/electricdss/code/4175/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Adding unified interface to the DLL as alternative for exposing the code as infrastructure.&lt;br/&gt;&lt;a href="/p/electricdss/code/4175/"&gt;View Changes&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">davismont</dc:creator><pubDate>Sat, 05 Sep 2026 12:07:18 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net/p/electricdss/code/4175/</guid></item><item><title>OpenDSS Visualizer</title><link>https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#6d4b</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Meisam Ansari</dc:creator><pubDate>Fri, 04 Sep 2026 03:01:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0cb3ed0047e48579d6e8c35ec2c44703f8894208</guid></item><item><title>OpenDSS Visualizer</title><link>https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#129b</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Meisam Ansari</dc:creator><pubDate>Fri, 04 Sep 2026 03:01:21 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net782d855ded3783bacb866709968bcdf659c117a2</guid></item><item><title>Mathematical Method</title><link>https://sourceforge.net/p/electricdss/discussion/861977/thread/7473cb25/?limit=25#e27f</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hamza</dc:creator><pubDate>Thu, 03 Sep 2026 16:27:06 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net80fae0d4aaa96c4299e21e83c07755f304708708</guid></item><item><title>Struggling to get GFM Storage to sustain output past 1 timestep (IEEE 13-bus)</title><link>https://sourceforge.net/p/electricdss/discussion/861977/thread/29187f3275/?limit=25#b23c</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sergio Miguel</dc:creator><pubDate>Mon, 24 Aug 2026 19:42:46 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6dd20b2f48b79abb236776988421c27a2111ed34</guid></item><item><title>OpenDSS Visualizer</title><link>https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#2428/48fa/ae0f/2d71/65d6/1e0d</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Davis Montenegro</dc:creator><pubDate>Mon, 24 Aug 2026 14:50:39 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net107554d27fd80ed8b4709ec81d063402b0ac8290</guid></item></channel></rss>