search

nikhilgupta10 / GridLAB-D

Other
1 stars 0 forks source link

#766 Implement engine support for GridLAB-D, #1495

Open nikhilgupta10 opened 8 years ago

nikhilgupta10 commented 8 years ago

Create a glengine class library and matching glxengine link to allow external application to start and interact with gridlabd instances.

,

nikhilgupta10 commented 8 years ago

nikhilgupta10 imported these comments from Sourceforge: The user dchassin does not exist anymore. Therefore assigning this to afisher1.

Diff:

I was able to successfully integrate the code into trunk. However, there is an autotest in core/link/engine/autotest/ called test_engine. Now, this test seems to run forever and not exit. I have to kill it. I've tried putting a clock object in the test to try and cause it to stop with no luck. I'm wondering if it's trying to connect with something and failing to time out? here is the output from when I run it.

, Andy,

Could this be related to ticket 942?

https://sourceforge.net/p/gridlab-d/tickets/942/, I don't think the autotest looks finished. I believe the engine code is done though, but I would really need to spend some time looking at it.

There's no harm in adding a alidate.no\ file to the engine folder for now if you want to disable validation until I have a chance to inspect the code., That's not the most likely cause of this problem. It looks like I didn't finish the autotest. It's supposed to creates a gridlabd server using a script call, link to the server, run a short model and shut everything down. I'm guessing that I forgot to checkin code on one of my machines, either on my personal machine or at UVic. It'll be a few weeks before I can inspect my old VMs and be certain., Thanks Dave. That's what I believe is the problem. I've committed the code to Trunk with a validate.no file so that it doesn't run the autotest., Further work is needed but this is no longer blocking knothole activities. Postponing to future milestone.,