I extract the first two with a "Redim Preserve t(1)" command.
In the first case, the redim is correct, Line 7 = Line 2 and Line 8 = Line 3. It just kept the first two values like it is supposed to be.
But, for the second curve starting Line 9, some t values are messed up after the Redim. Line 16 = Line 17 despite Line 11 was different from Line 12. That's what is creating a problem later in the Split.
Weird.
…
r surfaces by EP results' components.
Having set a period from 9:00 to 19:00 for a single day (10th december), and using a slider from 0 to 10 (11 values, 0 is 9:00), the following mismatch occurs:
setting value 0 works for surface temperature but not for mean radiant temperature (warning says "stepofSimulation is outside the bounds of the comfResultMTX", but I do have 11 values from radiant temp matrix).
setting value 1 is rendered as "hour 2 of simulation" for surface temperature (FIG 1) and as "9:00" of radiant temperature (FIG 2).
It seems there is a slide of 1 hour. How should I interpret this?
Kind regards,
artemátyika…
Added by artemátyika at 3:34pm on February 2, 2019
NONE, in SIZING:PARAMETERS". I'm not sure of where to start in troubleshooting this. I've attached the file.
Thank you,
See the errors and warnings below:
{0;0;0}
0. Current document units is in Meters
1. Conversion to Meters will be applied = 1.000
2. [1 of 8] Writing simulation parameters...
3. [2 of 8] Writing context surfaces...
4. [2 of 8] Writing context surfaces...
5. [3 of 8] Writing geometry...
6. [4 of 8] Writing Electric Load Center - Generator specifications ...
7. [5 of 8] Writing materials and constructions...
8. [6 of 8] Writing schedules...
9. [7 of 8] Writing loads and ideal air system...
10. [8 of 8] Writing outputs...
11. ...
... idf file is successfully written to : R:\Green\SuRG\Building_Performance_Analysis\2016_analysis_studies\Energy_Analysis_Comparison\Honeybee_+_Ladybug\tutorial01\EnergyPlus\tutorial01.idf
12.
13. Analysis is running!...
14. ...
...
Done! Read below for errors and warnings:
15.
16. Program Version,EnergyPlus, Version 8.5.0-c87e61b44b, YMD=2016.10.31 11:39,IDD_Version 8.5.0
17.
18. ************* IDF Context for following error/warning message:
19.
20. ************* Note -- lines truncated at 300 characters, if necessary...
21.
22. ************* 24 Sizing:Parameters,
23.
24. ************* Only last 1 lines before error line shown.....
25.
26. ************* 25 None, !- Heating Sizing Factor
27.
28. ** Severe ** IP: IDF line~25 Invalid Number in Numeric Field#1 (Heating Sizing Factor), value=NONE, in SIZING:PARAMETERS
29.
30. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
31.
32. ** ~~~ ** Possible Invalid Numerics or other problems
33.
34. ** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
35.
36. ...Summary of Errors that led to program termination:
37.
38. ..... Reference severe error count=1
39.
40. ..... Last severe error=IP: IDF line~
, value=NONE, in SIZING:PARAMETERS
41.
42. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
43.
44. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
45.
46. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
47.
48. ************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors.
49.
50. ************* EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 9.34sec
51.…
fault materials...6 RAD materials are loaded1. 2. Downloading OpenStudioMasterTemplate.idf to c:\ladybug\3. Loading EP construction library4. 206 material found in c:\ladybug\OpenStudioMasterTemplate.idf5. 30 windowmaterial found in c:\ladybug\OpenStudioMasterTemplate.idf6. 284 construction found in c:\ladybug\OpenStudioMasterTemplate.idf7. Loading EP schedules...8. The ScheduleTypeLimits: Fraction is already existed in the libaray.You need to rename this ScheduleTypeLimits.9. The ScheduleTypeLimits: Temperature 7 is already existed in the libaray.You need to rename this ScheduleTypeLimits.10. 21 scheduletypelimits found in c:\ladybug\OpenStudioMasterTemplate.idf11. 1370 schedule found in c:\ladybug\OpenStudioMasterTemplate.idf12. 13. 14. Hooohooho...Flying!!Vviiiiiiizzz...…
nique name like in your example {0;0},{0;1},{0;2},{0;3} where each path contains 11 elements(curves,points,values,etc)
so if you want to restructure the structure first right click on path mapper and take create null mapping which reads your current path structure into the component
after that you can additional write on the left side to the existing path (i) as variable for the elements and then on the right side type in the structure you want to achieve
maybe {A;i}(B) so after that you have 11 paths where each have 3 elements
hope that helps…
here are 11 numbers (0 to 10), and a 'step' of 42 (0 to 42 to 84), and I need to be able to 'cap' the number of times the 11 numbers are added, for example 3 for the list above.
I'm sure this is simple, and I'm kicking myself that I can't figure it out for myself, so any help would be greatly appreciated!…
nd this is the error text:
0. Current document units is in Meters1. Conversion to Meters will be applied = 1.0002. [1 of 8] Writing simulation parameters...3. [2 of 8] No context surfaces...4. [3 of 8] Writing geometry...5. [4 of 8] Writing Electric Load Center - Generator specifications ...6. [5 of 8] Writing materials and constructions...7. [6 of 8] Writing schedules...8. [7 of 8] Writing loads and ideal air system...9. [8 of 8] Writing outputs...10. ...... idf file is successfully written to : C:\Users\Pier\Desktop\Dottorato\Energy_plus_file\cell room\EnergyPlus\cell room.idf11. 12. Analysis is running!...13. C:\Users\Pier\Desktop\Dottorato\Energy_plus_file\cell room\EnergyPlus\eplusout.csv14. ......
Done! Read below for errors and warnings:
15.
Thanks in advance to all for your help me
Francesco…
can gain that much. If you used nested "if else" statements or "andalso" statements in the previous version most of the iterations should stop after the first distance comparison.…
Added by Vicente Soler at 2:36pm on December 1, 2012