Closed Myoldmopar closed 10 years ago
The weather file need to be in sync with the number of time steps only when the weather file does not use hourly data. Both weather files use hourly data. The question is, why is NumIntervalsPerHour != 1 ?
There's only 1 occurrence of the first warning below in the code:
if ( GetInputFlag ) {
SetupInterpolationValues();
TimeStepFraction = 1.0 / double( NumOfTimeStepInHour );
OpenWeatherFile( ErrorsFound ); // moved here because of
possibility of special days on EPW file CloseWeatherFile(); ReadUserWeatherInput(); AllocateWeatherData(); if ( NumIntervalsPerHour != 1 ) { if ( NumIntervalsPerHour != NumOfTimeStepInHour ) { <- first severe error ShowSevereError( RoutineName + "Number of intervals per hour on Weather file does not match specified number of Time Steps Per Hour" ); ErrorsFound = true; } } GetInputFlag = false; Envrn = 0; if ( NumOfEnvrn > 0 ) { ResolveLocationInformation( ErrorsFound ); // Obtain weather related info from input file <- second warning issued here CheckLocationValidity(); if ( Environment( NumOfEnvrn ).KindOfEnvrn != ksDesignDay ) { CheckWeatherFileValidity(); } if ( ErrorsFound ) { ShowSevereError( RoutineName + "No location specified, program will terminate." ); }
On 7/1/2014 5:13 PM, Edwin Lee wrote:
- Running on Linux; not sure if it is a factor elsewhere.
- Running a modified PlantLoadProfile to test configurations for
4333 https://github.com/NREL/EnergyPlusTeam/issues/4333
- Site:Location is for Chicago
- Weather file happened to be Golden, CO
Program was terminating with a fatal error. Error file contents:
Program Version,EnergyPlus, Version 8.1, YMD=2014.07.01 15:03,IDD_Version 8.1.0.009 * Severe * GetNextEnvironment: Number of intervals per hour on Weather file does not match specified number of Time Steps Per Hour * Warning * Weather file location will be used rather than entered (IDF) Location object. * ~~~ * ..Location object=CHICAGO_IL_USA_WMO_725300 * ~~~ * ..Weather File Location=Golden CO USA Custom-724666 WMO#=724666 * ~~~ * ..due to location differences, Latitude difference=[2.26] degrees, Longitude difference=[17.30] degrees. * ~~~ * ..Time Zone difference=[1.0] hour(s), Elevation difference=[862.63] percent, [1639.00] meters. * Severe * GetNextEnvironment: No location specified, program will terminate. * Fatal * Previous Conditions cause program termination. ...Summary of Errors that led to program termination: ..... Reference severe error count=2 ..... Last severe error=GetNextEnvironment: No location specified, program will terminate. ***** Warning: Node connection errors not checked - most system input has not been read (see previous warning). ***** Fatal error -- final processing. Program exited before simulations began. See previous error messages. ***** EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors. ***** EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors. ***** EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 2 Severe Errors; Elapsed Time=00hr 00min 3.00sec Seeming to be a problem with the Site:Location object...but there wasn't an issue. I then ran it with Chicago weather and it ran just fine. I looked in the code and found this block https://github.com/NREL/EnergyPlusTeam/blob/develop/src/EnergyPlus/WeatherManager.cc#L549-L554 that seems it could be the culprit. Maybe the check validity call is not doing something properly, or not initializing the "return value" (ErrorsFound)...not sure.
— Reply to this email directly or view it on GitHub https://github.com/NREL/EnergyPlusTeam/issues/4342.
Richard Raustad Senior Research Engineer Florida Solar Energy Center 1679 Clearlake Road Cocoa, FL 32922 Ph: (321)638-1454 http://www.fsec.ucf.edu/en/
Electric Vehicle Transportation Center http://evtc.fsec.ucf.edu/
@myoldmopar @rraustad Sounds like something's messed up in the "Golden" weather file that was run. Granted, if the timestep interval mismatch error trips, that really should be the end of things.
On 7/2/2014 7:29 AM, Richard Raustad wrote:
The weather file need to be in sync with the number of time steps only when the weather file does not use hourly data. Both weather files use hourly data. The question is, why is NumIntervalsPerHour != 1 ?
There's only 1 occurrence of the first warning below in the code:
if ( GetInputFlag ) {
SetupInterpolationValues(); TimeStepFraction = 1.0 / double( NumOfTimeStepInHour );
OpenWeatherFile( ErrorsFound ); // moved here because of possibility of special days on EPW file CloseWeatherFile(); ReadUserWeatherInput(); AllocateWeatherData(); if ( NumIntervalsPerHour != 1 ) { if ( NumIntervalsPerHour != NumOfTimeStepInHour ) { <- first severe error ShowSevereError( RoutineName + "Number of intervals per hour on Weather file does not match specified number of Time Steps Per Hour" ); ErrorsFound = true; } } GetInputFlag = false; Envrn = 0; if ( NumOfEnvrn > 0 ) { ResolveLocationInformation( ErrorsFound ); // Obtain weather related info from input file <- second warning issued here CheckLocationValidity(); if ( Environment( NumOfEnvrn ).KindOfEnvrn != ksDesignDay ) { CheckWeatherFileValidity(); } if ( ErrorsFound ) { ShowSevereError( RoutineName + "No location specified, program will terminate." ); }
On 7/1/2014 5:13 PM, Edwin Lee wrote:
- Running on Linux; not sure if it is a factor elsewhere.
- Running a modified PlantLoadProfile to test configurations for
4333 https://github.com/NREL/EnergyPlusTeam/issues/4333
- Site:Location is for Chicago
- Weather file happened to be Golden, CO
Program was terminating with a fatal error. Error file contents:
Program Version,EnergyPlus, Version 8.1, YMD=2014.07.01 15:03,IDD_Version 8.1.0.009 * Severe * GetNextEnvironment: Number of intervals per hour on Weather file does not match specified number of Time Steps Per Hour * Warning * Weather file location will be used rather than entered (IDF) Location object. * ~~~ * ..Location object=CHICAGO_IL_USA_WMO_725300 * ~~~ * ..Weather File Location=Golden CO USA Custom-724666 WMO#=724666 * ~~~ * ..due to location differences, Latitude difference=[2.26] degrees, Longitude difference=[17.30] degrees. * ~~~ * ..Time Zone difference=[1.0] hour(s), Elevation difference=[862.63] percent, [1639.00] meters. * Severe * GetNextEnvironment: No location specified, program will terminate. * Fatal * Previous Conditions cause program termination. ...Summary of Errors that led to program termination: ..... Reference severe error count=2 ..... Last severe error=GetNextEnvironment: No location specified, program will terminate. ***** Warning: Node connection errors not checked - most system input has not been read (see previous warning). ***** Fatal error -- final processing. Program exited before simulations began. See previous error messages. ***** EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors. ***** EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors. ***** EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 2 Severe Errors; Elapsed Time=00hr 00min 3.00sec Seeming to be a problem with the Site:Location object...but there wasn't an issue. I then ran it with Chicago weather and it ran just fine. I looked in the code and found this block
https://github.com/NREL/EnergyPlusTeam/blob/develop/src/EnergyPlus/WeatherManager.cc#L549-L554
that seems it could be the culprit. Maybe the check validity call is not doing something properly, or not initializing the "return value" (ErrorsFound)...not sure.
— Reply to this email directly or view it on GitHub https://github.com/NREL/EnergyPlusTeam/issues/4342.
Richard Raustad Senior Research Engineer Florida Solar Energy Center 1679 Clearlake Road Cocoa, FL 32922 Ph: (321)638-1454 http://www.fsec.ucf.edu/en/
Electric Vehicle Transportation Center http://evtc.fsec.ucf.edu/
— Reply to this email directly or view it on GitHub https://github.com/NREL/EnergyPlusTeam/issues/4342#issuecomment-47769529.
OK, I'm going to close this as invalid. I understand now that the weather file and zone time step interact as such:
Program was terminating with a fatal error. Error file contents:
Seeming to be a problem with the Site:Location object...but there wasn't an issue. I then ran it with Chicago weather and it ran just fine. I looked in the code and found this block that seems it could be the culprit. Maybe the check validity call is not doing something properly, or not initializing the "return value" (ErrorsFound)...not sure.