search

nikhilgupta10 / GridLAB-D

Other
1 stars 0 forks source link

#892 Internal invalid timestamp error during processing, #2618

Open nikhilgupta10 opened 7 years ago

nikhilgupta10 commented 7 years ago

The attached GLM file generates the following error:

FATAL    [2014-01-01 00:00:00 EST] : Invalid day provided in datetime
ERROR    [2014-01-01 00:00:00 EST] : local_datetime(ts=1,...): invalid local_datetime request
~~~~~,
nikhilgupta10 commented 7 years ago

nikhilgupta10 imported these comments from Sourceforge: The user dchassin does not exist anymore. Therefore assigning this to afisher1. "dchassin":FYI, this seems to be related to setting triplex_meter.bill_day > 28.,

"dchassin":- Priority: blocker --> major ,

"jcfuller":From wiki:

bill_day int32 N/A Sets the date of the month at which the final monthly bill is calculated (at midnight). Maximum value is 28.

Looks like we just need to add a catch for when it is set greater than 28.,

"dchassin":Agree. Also note that setting it to 1 bills on the last day of the month. Not sure what zero default does.

Dave

On Sep 21, 2014, at 22:56, \Jason Fuller\ jcfuller@users.sf.net wrote:

From wiki:

bill_day int32 N/A Sets the date of the month at which the final monthly bill is calculated (at midnight). Maximum value is 28.

Looks like we just need to add a catch for when it is set greater than 28.

\ [tickets:#892] Internal invalid timestamp error during processing**

Status: new Milestone: Version 3.1 Stable Created: Sun Sep 21, 2014 07:56 PM UTC by David P. Chassin Last Updated: Sun Sep 21, 2014 07:59 PM UTC Owner: nobody

The attached GLM file generates the following error:

FATAL    [2014-01-01 00:00:00 EST] : Invalid day provided in datetime
ERROR    [2014-01-01 00:00:00 EST] : local_datetime(ts=1,...): invalid local_datetime request

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/gridlab-d/tickets/892/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/,

"jcfuller":We could have it default to '-1', which would indicate o billing. '0' could then be used to indicate ill on the last day of the month.

Note, that the bill is process at midnight, so setting the bill date to 1 is really capturing the bill for the entirety of the previous month.,

"dchassin":It may be sufficient to just document what 0 and 1 do. By the way, I can't be sure what 0 actually does because it causes the attached model to hang after emitting the invalid day error.,

"dchassin":I'm ok with it as it works now. I say document it and fix the bug, if it's really a bug and not a missing default or error check. Just took me a while to figure it out.

D.

On Sep 22, 2014, at 9:54 AM, \Jason Fuller\ jcfuller@users.sf.net wrote:

We could have it default to '-1', which would indicate o billing. '0' could then be used to indicate ill on the last day of the month.

Note, that the bill is process at midnight, so setting the bill date to 1 is really capturing the bill for the entirety of the previous month.

\ [tickets:#892] Internal invalid timestamp error during processing**

Status: new Milestone: Version 3.1 Stable Created: Sun Sep 21, 2014 07:56 PM UTC by David P. Chassin Last Updated: Mon Sep 22, 2014 05:56 AM UTC Owner: nobody

The attached GLM file generates the following error:

FATAL    [2014-01-01 00:00:00 EST] : Invalid day provided in datetime
ERROR    [2014-01-01 00:00:00 EST] : local_datetime(ts=1,...): invalid local_datetime request

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/gridlab-d/tickets/892/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/,

"dchassin":- Owner: Anonymous --> David P. Chassin