Cumulus Support

Posted: **Wed 12 Jun 2024 7:22 pm**

I get following error when running Cumulusutils.
In those error field i do not get any value, just coma field separators (,,,,)

Code: Select all

2024-06-12 21:15:10.424 CumulusUtils Initial: Shutting down the default listener
2024-06-12 21:15:10.475  CUstrings[xx].ini : CUstringsEN.ini looked for.
2024-06-12 21:15:10.495  CumulusUtils version: 7.0.3 
2024-06-12 21:15:10.496  CuSupport constructor : Unit Wind (m/s, mph, km/h, kts): km/hr
2024-06-12 21:15:10.497  CuSupport constructor : Unit Pressure (mb,hPa,inHg): hPa
2024-06-12 21:15:10.498  CuSupport constructor : Unit Rain (mm,in): mm
2024-06-12 21:15:10.499  CuSupport constructor : Unit T (C,F): Â°C
2024-06-12 21:15:10.500  CuSupport constructor : Unit Distance (m, mi, km, kn): km
2024-06-12 21:15:10.501  CuSupport constructor : Unit Height (m, ft): m
2024-06-12 21:15:10.517 InetSupport: Constructor start
2024-06-12 21:15:10.971 InetSupport: Plain Old FTP activated.
2024-06-12 21:15:10.979 CumulusUtils : ----------------------------
2024-06-12 21:15:10.979 CumulusUtils : Entering Main
2024-06-12 21:15:10.984 HelpTexts: starting
2024-06-12 21:15:11.056 CommandLineArgs : starting
2024-06-12 21:15:11.056  CommandLineArgs : handling arg: pwsFWI
2024-06-12 21:15:11.058 Dayfile: Reading the dayfile.txt...
DayfileValue.SetValues fail: The input string '' was not in a correct format.
DayfileValue.SetValues: in field nr 40 (heatingdegreedays)
DayfileValue.SetValues fail: The input string '' was not in a correct format.
DayfileValue.SetValues: in field nr 40 (heatingdegreedays)
DayfileValue.SetValues fail: The input string '' was not in a correct format.
DayfileValue.SetValues: in field nr 40 (heatingdegreedays)
2024-06-12 21:15:11.336 calculatePwsFWI : starting
2024-06-12 21:15:11.336 calculatePwsFWI : ANALYSE is OFF

Posted: **Wed 12 Jun 2024 8:49 pm**

Could you post your dayfile please.

Another point is that what you post is not the logfile but the console screenoutput.
Please post the complete logfile as well (it gives me the line number)

(and if possible set the URL for the usermap to the pwsFWI location?)

Posted: **Fri 14 Jun 2024 6:04 pm**

Dayfile and cumulusutils log file attached

Posted: **Fri 14 Jun 2024 7:38 pm**

vpokroglo wrote: ↑Fri 14 Jun 2024 6:04 pm Dayfile and cumulusutils log file attached

OK... The lines are from 29/04/11, 30/04/11 and 04/08/11 so apparently on those days something went wrong.

As such it is not a problem of CUtils but CMX apparently did not store those data (it occurs only on those three days).

When modifying the dayfile, shutdown CMX, when done, restart CMX.

If you still have the original monthly logs for those months I think you best run CreateMissing and see if that has the desired effect (a correct dayfile).
If you don't get a correct dayfile, I suggest you just fill in the values yourself. It is then best to take the values of the day before (make sure you pick the correct fields) and paste them in the correct position of the erroneous lines.

Let me know how you get on.
(and please fill in the pwsFWI link in your cumulusutils.ini map link parameter)

Posted: **Fri 14 Jun 2024 11:50 pm**

Hi,
Those ,,,,,,'s appear in about 49 lines of your dayfile.
My suggestion is to delete all of the lines with those and then do a CreateMissing as Hans suggested.
Before deleting the lines do a backup of the dayfile.txt so you will have a good part of those days still intact if you need to use that for manual editing.

Enjoy,
Paul

Posted: **Sat 15 Jun 2024 5:41 am**

PaulMy wrote: ↑Fri 14 Jun 2024 11:50 pm Those ,,,,,,'s appear in about 49 lines of your dayfile.

Thanks for the additional precision @Paul.

I can add that the of 49 times you saw, only the three lines I mention have impact on the functioning of CUtils. Because the data which CUtils requires are missing in those lines as you can see in the log. The other missing data are not used.

So if CreateMissing fails and you need to edit the dayfile then only those three lines require treatment.
The user can decide to (not) repair the other lines.

Posted: **Sun 16 Jun 2024 10:37 am**

Also cretemissing utility doesn't work for me... It doesn't do anything to dayfile.txt. log is attached.

Posted: **Sun 16 Jun 2024 11:31 am**

vpokroglo wrote: ↑Sun 16 Jun 2024 10:37 am Also cretemissing utility doesn't work for me... It doesn't do anything to dayfile.txt. log is attached.

Hi,

The logfile says it does not have the datafiles for the records so it can't change values. So the only option left is to edit the dayfile.

Goto to the Dayfile editor in the CMX interface (Data Logs=>Dayfile) and goto the records on the dates I indicated above.
Give the records values for the heatingdegreedays and the Coolingdegreedays. Any value will do, but I advise to give the value of the day before. Save the modified record.

Then reload dayfile.

Then run CUtils again. If the error occurs with another value in the dayfile then repeat until your dayfile passes without error.

Posted: **Sun 16 Jun 2024 12:20 pm**

Yes I know, that some days are missing in logfiles, but look at last 4 days after 11.6.2024 (12.6, 13.6, 14.6, and 15.6). Createmissing says that it added those missing entries, but it doesn't.

Posted: **Sun 16 Jun 2024 12:30 pm**

You will have to address CreateMissing issues in the CMX forum. This is the CUtils forum and I gave the solution related to CUtils (which I think will help you quickly).

For the problems related to CreateMissing please create a topic in teh CMX forum containing the description and the related files (logs and old dayfile and reaulting dayfile). I am no specialist here.

Cumulus Support

The input string '' was not in a correct format.

The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.

Re: The input string '' was not in a correct format.