Hi Achim,<br><br>Thanks for taking the time to reply.<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
(1) The variable names in RES are quite often somewhat misleading. For solar radiation, I have found it easiest / best to add a small surface with absorptivity of 1.0 as "sensor" on each elevation of interest.<br>
<br></blockquote><div>Just curious regarding your reasoning for creating a sensor versus using the output from built-in variables. Have you found certain variables personally to be inaccurate with regards to incident solar energy? What is considered to be 'best practice' for extraction of incident solar radiation?<br>
<br>My main concern in using a point sensor is that some modelling complexity with regards to self-shading via the insolation and shading module would be ignored or moreover the sensor might be placed by accident in a partially shaded area (please note that I am developing an optimization procedure that auto-generates geometry, and hence would require auto-sensor placement based on geometry). <br>
<br>I am completely in favor, if both methods yield similar results regardless of shading.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
(2) There is an additional output possibility: xml. If your model is not too large / complex, the runtime increase when using xml output is not too dire. All you need is a compile with xml support and an input.xml file in the calling directory of esp-r. After a short run (a few timesteps) a file "dictionary" is created. This lists all available output. Then, the input.xml can be extended to whatever output you require and there is no limit to columns ...<br>
<br></blockquote><div>I have played around a little with XML support but gave up when I discovered how to use RES via scripts. I am dealing with a lot of data, hourly time steps, annual simulation with electrical, air-flow networks, etc... So time taken to write to a text file adds up quickly. I found RES to be much more streamlined as I can extract specific variables from the res db file.<br>
<br>The only option I am familiar with the output xml is the 'dump all data' option. Are there options to output specific variables? Any documentation on this? Is XML support still considered to be experimental?<br>
<br>Scott<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div><br>
<br>
<br>
On Sep 15, 2009, at 7:46 PM, Scott Bucking wrote:<br>
<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div>
Hi all,<br>
<br>
I'm running a simulation that looks at incident solar energy on a building surface and noticed a few things that I was hoping someone could clarify.<br>
<br>
First is that 'SW incident solar' appears not to work for transparent surfaces. Should I be using 'Solar processes' and select 'solar entering from outside'? Or is this accounted for in the overall building surface?<br>
<br>
Also, it appears that RES limits data output to 10 columns (anymore then 10 surfaces appears to be cutoff from the GRT output file). Is it possible to recompile ESPr and change this to, say 20 columns? What was the original thought in limiting it to ten?<br>
<br>
Kind Regards,<br>
<br>
Scott<br></div></div>
_______________________________________________<br>
esp-r mailing list<br>
<a href="mailto:esp-r@lists.strath.ac.uk" target="_blank">esp-r@lists.strath.ac.uk</a><br>
<a href="http://lists.strath.ac.uk/mailman/listinfo/esp-r" target="_blank">http://lists.strath.ac.uk/mailman/listinfo/esp-r</a><br>
</blockquote>
<br>
<a href="mailto:achim.geissler@intergga.ch" target="_blank">achim.geissler@intergga.ch</a><br>
<br>
<br>
<br>
<br>
</blockquote></div><br>