FAQ: Difference between revisions

← Older edit

FAQ (view source)

Revision as of 12:08, 27 January 2023

1,128 bytes removed , 27 January 2023

→‎Cumulus isn't performing periodic tasks, like data logging or web uploads

Mcrossley

Bureaucrats, Administrators

1,167

edits

Revision as of 19:36, 26 July 2020 (view source) Sfws (talk \| contribs) m (→‎Cumulus read some invalid figures from my station) ← Older edit		Latest revision as of 12:08, 27 January 2023 (view source) Mcrossley (talk \| contribs) (→‎Cumulus isn't performing periodic tasks, like data logging or web uploads)
(23 intermediate revisions by 4 users not shown)
(consult also the Help screens within Cumulus software, and learn more from the rest of this Wiki) ~~Some~~A ~~references~~separate toFAQ ~~other~~was ~~flavours of Cumulus are included here. There is also a separate FAQ~~created specifically for [[Cumulus MX FAQ~~\|Cumulus MX~~]]. = Installing and Running Cumulus = == What operating systems does Cumulus run on? == Cumulus 1 - All versions of Windows from XP to Windows 1011 inclusive (and the server versions). It works on 32 bit and 64 bit editions. ~~It may also work on Windows 2000, but this is not supported. You will probably not be able to get it to work on Windows 2000 with a Fine Offset station.~~ {{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1 Davis Vantage Pro (VP), Vantage Pro2 (VP2), and Vue (the Envoy8X and Weatherlink Live is '''not''' supported). Oregon Scientific WM918, WMR918, WMR928, WMR968, WMR88 (see [[FAQ#How do I set up recording wind speeds in Cumulus, with Oregon Scientific and La Crosse stations \| this FAQ]]), WMR100, WMR180, WMR200. Fine Offset - USB-connected stations which use the Easyweather software such as MyDEL, Nevada, Watson and Fine Offset, with model numbers such as WH1080, WH1081, W8681, 265NC etc. {{Version badge 1}}Reminder, this FAQ answer is ONLY for Cumulus 1 As of 2017, development of ~~both~~ Cumulus 1 ~~and Cumulus MX~~ was ~~abandoned~~stopped by Steve Loft and a new version called '''Cumulus MX beta''' replaced it. Although there have been a couple of patches to change the years listed in drop downs with Cumulus 1, its code is frozen as the relevant development environment is no longer available. Consequently, there is no possibility of any new features for Cumulus 1. == What are the formats of the Cumulus data files? == These are detailed in the [[:Category:Log Files\|Log Files]] section of this Wiki, see that category page for key information about log files and the ~~differences between the Cumulus 1 and Cumulus MX~~ content. Format information is also in the Cumulus 1 help file, in the section “Data log file format” Davis station firmware supplies two wind speeds, a 3-second average and a 10-minute average (later versions of the firmware also supply a 2-minute average, Cumulus currently doesn't use this). The latest Davis 3-second average is treated by Cumulus as 'Latest' (available via <#wlatest>, matching direction is '<#currentwdir>' and '<#bearing>') * The highest of the station's 3-second readings over the previous 10 (configurable by adding ''AvgSpeedMinutes=N'' in [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station]] where 'N' is number of) minutes becomes the Cumulus 'Gust (available via <#wgust>, no matching direction web tag). Note that the WMO definition of a wind gust is the mean wind speed over a 2 to 3 second sample period (so Cumulus reports this within an extended 10, or as configured, minute period, not the 'latest' gust). * The Davis 10-minute average is the Cumulus 'Average' (available via <#wspeed>, matching direction reported as '<#wdir>' and '<#avgbearing>'). ** If 'Calculate 10-min wind average' and 'Use speed for avg calculation' are both selected; the average of the Fine Offset 'Wind' values read over the previous N (configurable, defaults to 10) minutes is reported. Select value for 'N' using ''AvgSpeedMinutes=N'' in [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station]]. == How do I set up recording wind speeds in Cumulus 1, with Oregon Scientific and La Crosse stations == La Crosse and some Oregon Scientific weather stations only output a single wind speed. To allow Cumulus to calculate 'gust' and 'wind speed' with different values, select the '''Station''' dialogue from the ''Configuration'' menu and set ''Calculate 10 min wind average'' in the 'Settings' frame, so in [[cumulus.ini]] this will produce the parameter 'Wind10MinAverage=1 when cumulus is next stopped. * The station's 'Wind' value will then display as Cumulus 'Latest'. * A 10 (configurable by adding ''AvgSpeedMinutes=N'' in [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station]] where 'N' is number of) minutes average of the station's 'Wind' value will then display as Cumulus 'Average'. * The highest of the station's 'Wind' value in a 10 minute period will then display as Cumulus 'Gust'. Note that the WMO definition of a wind gust is the mean wind speed over a 2 to 3 second sample period (not the maximum instantaneous wind speed). See ''LCMaxWind=X'' parameter in [[Cumulus.~~ini~~ini_(Cumulus_1)#La_Crosse_specific:]] where X is the maximum (uncalibrated) wind speed in m/s that you want to allow. == How do I make Cumulus 1 run automatically when Windows starts? == Don't forget that Cumulus uses binary arithmetic to base 2, that does not correctly represent what in base 10 are decimal places, so you may see slight errors for those using inches and expecting correctness to two decimal places (read up this on internet if you don't understand binary arithmetic). The rainfall totals shown on the ''This period'', ''This month'', and ''This year'' screens within the '''View''' menu in Cumulus 1 are generated by adding up the daily rainfall totals found in [[dayfile.txt]] for the selected period. Using default settings via '''View''' menu in Cumulus 1, ''This month'' screen for this month excluding today, ''This year'' screen for this calendar year (this does always start on 1 January, unless you only started using Cumulus after that) excluding today. ''Note any rainfall for the current (meteorological) day is excluded as the latest dayfile.txt row is for yesterday.'' Totals can be shown for any past period, by selecting the required dates, the figures are recalculated when you press the ''Update display'' button and will include all days available in dayfile.txt for the chosen period. ''Important note: The view menu 'This year' screen always calculates the total for a selected calendar year starting in January.'' ** Cumulus MX builds below 3008 do not include rainfall for year to date, other rainfall calculation items were fixed in 3022 to 3042, you should use latest build for best functionality. * Each time Cumulus ~~(both 1 and MX)~~ reads records from the weather station it applies any change to the 'total rain count' against today's total in its memory. This "Count" approach has been chosen because different weather stations output different values, and an independent count is a way of working that can be applied for any weather station. As you will see if you look in [[~~diags~~diags_folder]], Cumulus stores the 'total rain count' figure at rollover, so by maintaining the current figure it can subtract off the start of day figure to deduce the rainfall today and this is shown on the front screen in Cumulus 1, labelled ''Today''. In Cumulus 1 the '''Edit''' menu gives access to the ''Today's rain'' screen and that provides the ability to edit the start of day figure so that the figure shown for today is correct~~. Equivalent functionality is provided in Cumulus MX. If there is no rain in a day, the start of day count will be the same at the start of the next day~~. If there is no rain in a day, the start of day count will be the same at the start of the next day. Today's rain is added to the figures (as described above) derived from dayfile.txt for what the front screen in Cumulus 1, labels '''This month''', and ''This year'' (this last figure is the seasonal total, you can choose for it to start on 1 January or any other month). Thus these figures are updated each time Cumulus receives a rain reading from the station (they all include today-so-far), and these figures will not be displayed if Cumulus is unable to read rain information from your station. The today's total so far at each reading time is also added to the 'recent tag' array allowing total values for the day-so-far at one minute intervals for up to a week ago to be added as web tags to a web template. * For the web tags, Cumulus ~~(both 1 and MX)~~ takes its stored sums and adds today's latest total each time, to give the current totals for this month and this rain season (year so far) when processing ''''indexT.htm'''' web template ~~which is where~~as these figures ~~ase~~are shown on that page (not on ''this month'' nor on ''this year'' templates). Important, for the <#ryear> web tag, and for the 'This year' display on the ''main'' Cumulus screen, the processing reads the ''dayfile.txt'' for the rainfall season starting with the month set on the station settings screen and stored as the value for attribute ''RainSeasonStart'' in [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station]] (its default is January). If you have set a 'year to date' value and Cumulus is being re-started when the year specified beside that figure matches the current calendar year, your year-to-date amount is also added into this year's total. This should normally only be relevant in your first rain season of operating Cumulus, but could be used if in any season you needed to add an extra amount because for some reason you had a gap in your recording period. ''Do be aware that if you select a rain season starting in a month other than January, the year to date figure will stop being added on 1 January because the year specified next to the figure to add on will then be the previous calendar year!'' *There is no corresponding setting for amending the total for the first 'this month' of Cumulus operation. The only way round this is to manually change the rainfall in dayfile.txt for the first day of operation to include rainfall on all previous days of month, but that could potentially cause you to set the maximum daily rainfall extreme record wrongly. Note that you need to stop and then restart Cumulus to update these initial values that are stored in memory and get any corrections you made to rogue values in the daily summary log (or year-to-date) reflected on the main Cumulus screen and in web tags. The built-in dayfile.txt editor is used if it is necessary to amend the daily totals (to correct any monthly, rain season, or calendar year, totals); the built-in all-time (or monthly records) editor(s) ~~in Cumulus 1 and MX~~ is used if it is necessary to regenerate the extreme records from dayfile.txt; see [[#My_station_invented_some_rain_that_didn.27t_really_occur.2C_and_I_want_to_set_it_to_zero_.28or_some_other_figure.29 \|FAQ about correcting incorrect rainfall displays]]. == How do I reset all my data to start again from scratch? == can all be customised by using the [[strings.ini]] file. '''This wiki page [[:Category:Other_Languages\|Other Languages]] has some obsolete (valid in 2009-2010) information about customising what were the standard web pages in versions of Cumulus 1 up to 1.8.x. The translations there are NOT compatible with later ~~(or final)~~ Cumulus 1 ~~version, nor will they work with Cumulus MX~~versions.''' On the downloads page you can find third-party alternative web pages, these typically include some language translation modules, but beware that these may not be maintained to work with latest versions of Cumulus. 3 options: You can install Cumulus 1 ~~(or MX)~~ on more than one machine, but each copy must connect directly to its own weather station (one station connected per Cumulus installation). You can install 2 copies of Cumulus 1 in different paths on a single PC, ''if you have two weather stations'' and Cumulus is able to distinguish between them, e.g. they are from different manufacturers, or both are serial port stations (different ports), or one is USB and one is serial, or one is a Weatherlink IP. In other words the combination that does not work on a single PC is two USB stations (including clones from different suppliers) from the same manufacturer. Note that Davis stations with USB loggers are serial port stations as far as Cumulus is concerned, so there are no problems using multiple copies of Cumulus with multiple Davis stations on the same PC. ~~(Same rules for two copies of Cumulus MX).~~ It is possible to back up the Cumulus files from one installation running off a weather station, and briefly have another reduced functionality copy just looking at historic data without ever any updating (the second Cumulus is set up as if reading from an EasyWeather.dat file, but not given a path/file name) - see [[Cumulus.~~ini~~ini_(Cumulus_1)#Introduced_for_problems_with_Fine_Offset_family:\|Easyweather.dat section here]]. Don't attempt to run Cumulus 1 and MX at same time, they cannot share a single weather station. However you can with a single weather station, stop Cumulus 1 and then run MX if they use different data folders, then later stop MX and run Cumulus 1. == I can't save my NOAA reports! == {{Version badge 1}}You've probably corrupted your Cumulus.~~ini~~ini_(Cumulus_1) file in the default Cumulus folder. See [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_NOAA]]. It can only be edited either (if Cumulus is stopped) with an external text file editor or (with Cumulus running) using the ''NOAA Setup'' in the configuation menu. Pay attention to where the quotes are required for the file names, and check that you have an allowed date format (see [[Webtags#The_format_used_for_naming]]). == My sunrise and sunset times are wrong == Do make sure you have exited out of the built-in viewer or editor before rollover is due. *If you inadvertently forget this, the cure of overwriting files mentioned above is applicable if your weather station has an internal log and it is around 2 logging intervals (see [[#Cumulus_takes_a_long_time_to_download_the_data_from_my_Davis_station_at_start_up]]) after rollover. When using an external editor, close Cumulus ~~1 or Cumulus MX~~ before opening any Cumulus file. == Why do I have some unexpected zero figures? == '''Fine Offset stations''' are prone to reporting the odd nonsensical value, and Cumulus has the ability to compare successive readings: {{Version badge 1}}From the '''Configuration''' menu select [[Cumulus_Screenshots#Configuration_Menu_Screens\|''Calibration'']] and in the '''Spike removal''' frame you can specify "the maximum '''differences''' between successive values" that Cumulus is to tolerate~~. See the '''Help''' for that screen, and note that spike removal applies while Cumulus is running, not to catch-up readings from the station's logger~~. {{Version badge 1}}See the '''Help''' for that screen, and note that '''spike removal applies while Cumulus is running''', it is not applied to catch-up readings from the station's logger. '''Possible Cure:''' The purpose of the backup files is to allow Cumulus to be 'rewound' to a particular point in time. It simulates the situation where someone had closed Cumulus down at that point, and is only now starting it up again, and needs data to be downloaded from the station's logger to catch up to the present time. Obviously this cure will not work if your station type does not have a logger (one is needed for Cumulus to read old readings again). If you have only installed Cumulus a few days ago, or have just re-started Cumulus after it was stopped and encounter multiple ''rogue readings in the catch-up from the station logger''; '''one possibility''' is to stop Cumulus and find the [[#On_restarting_Cumulus.2C_it_did_not_successfully_read_all_data_from_when_it_last_ran\|backup files]] that it took when you started it up (or just after the previous roll-over time), copy those files into the data folder, overwriting the ones that are there, then when you start it up again it will rewind back to the time in that back-up, and could sort itself out. {{Version badge 1}}The Cumulus 1 [[~~Diags~~Diags_folder\|Diagnostic]] log often contains useful information for sorting out what has been read, which values have been ignored, and which highs or lows may have been updated incorrectly. Note that automatic backups are made just after roll-over time because restarting Cumulus when there are no logger records to read before roll-over has been known to cause problems. Therefore, the backup to choose might be one with the date before when the problem occurred, but remember that any calculations Cumulus makes are based on readings at least every minute when Cumulus is running, but for the catch up period such calculations can only use the readings available at your station's logging interval. Note if you choose a later backup and it does not work, you can always then repeat the 'rewind' with a earlier backup. == How to restore a corrupted log file == Full information about all the log files is elsewhere [[:Category:Log_Files]], so you can study the notes linked from there, but here is a very quick summary. You may want to read [[Calculate_Missing_Values]] for more information. {{Version badge 1}}''These notes are written for Cumulus 1, some attempt is made to also cover Cumulus MX, but the way that date/times are stored in Cumulus 1 and Cumulus MX files can be different, particularly for the '.ini' files; consequently this summary does not cover any problems in files that have been ported from Cumulus 1 to Cumulus MX. '' Cumulus will create a copy of each of the logs (.ini and .txt) in the [[backup folder]], both at end of day rollover, and when the software is (re-)started. If the corrupted file in [[Data folder\|'data']] folder is a log file holding extremes (not the detailed log created for each month nor 'today.ini'), then the easiest way to remove false extremes recorded recently is to to overwrite the current file with the one from the most recent back-up. Both Cumulus 1 and Cumulus MX create a copy of each of the logs in the backup folder, both at end of day rollover, and when the software is (re-)started. If the corrupted file in 'data' folder is a log holding extremes (not the detailed log created for each month nor 'today.ini'), then the easiest way to remove false extremes recorded recently is to to overwrite the current file with the one from the most recent back-up. Since 'today.ini' is updated very frequently (every time Cumulus ~~interogates~~interrogates your weather station), it is not advised that you overwrite that file, unless you are able to do a rewind as described in [[#On_restarting_Cumulus.2C_it_did_not_successfully_read_all_data_from_when_it_last_ran\|earlier]] answer. If you were to use the backup folder copy of the detailed log, you would lose all of the stored values since the backup, so again only do that in a rewind context where all the files from the backup are overwriting those in data folder, and you simply want to copy in what is still in any station logging memory. If you were to use the backup folder copy of the detailed log, you would lose all of the stored values since the backup, so again only do that in a rewind context where all the files from the backup are overwriting those in data folder, and you simply want to copy in what is still in any station logging memory. {{Version badge 1}}Cumulus 1 provides editors - go to Edit menu and pick the relevant extremes file, the either type over the figures that you want to change or use the buttons that load the more detailed log files and then figures from them can be copied into extreme file. There is an option (in the view menu) to read the latest detailed log for the current (or past) month, but there is no built in editor for those files.▼ ▲~~{{Version badge 1}}~~Cumulus 1 provides editors - go to Edit menu and pick the relevant extremes file, the either type over the figures that you want to change or use the buttons that load the more detailed log files and then figures from them can be copied into extreme file. There is an option (in the view menu) to read the latest detailed log for the current (or past) month, but there is no built in editor for those files. ~~Cumulus MX (from version 3.2.2 - build 3058) provides editors for key log files (all-time and monthly-all-time).~~ You may want to read [[Correcting_Extremes]] for more information, but here is a summary. * Remember 'alltimelog.txt' logs each change made to 'alltime.ini' so you don't need to correct the former, but it can help you know how to regress the latter. * "speciallog.txt" (if used) holds internal temperature and internal humidity, it does not get copied to backup folder, so you need to back it up yourself. * 'yesterday.ini' will get overwritten at end of day, so it is rare to edit that. * "dayfile.txt" has a new line appended to it at the end of each day, if you go back to the backup copy and you lose the latest line, then most of the information can be extracted from the 'today.ini' in the same backup folder, but you need to understand the process and content differences as explained in the Wiki for the two files. * 'year.ini' and 'month.ini' record extremes shown for this year and this month, the diagnostics logs created in the sub-folder '[[diags_folder\|diags']] record each new extreme added to these files, so you can work through the diagnostic logs to identify what to correct. * "monthlyalltime.ini" is ~~essentaily~~essentially a more complicated 'month.ini', it separates out extremes for each month of year. Any change in the diagnostic logs for the current month may, or may not, affect "monthlyalltime.ini", but again searching through the logs should help. * 'log.xml' is another file that Cumulus does not copy to the backup folder, so you should back it up periodically. It is only found in Cumulus 1 and is edited using the 'Weather Diary' screen in the 'View' menu. Although it can be edited by a 'XML' editor, I advise against it, as the way that the field 'RowState' is calculated is complex, and if you corrupt the file, Cumulus 1 will crash. * "mmmyy.txt" (naming varies depending on computer settings) is the detailed log mentioned above Because many positive values are realistic, Cumulus generally will accept those odd increases as a result of accidental knocking of a tipping bucket gauge, due to wind effects on the gauge, or even due to the station electronics generating a rogue reading. The sub-answers below explain how to correct such errors. === (Invented rain) Error in today's total === Easy - correct today's total using the [[Today.ini#Editing_rainfall_in_today.ini_within_Cumulus \| 'today's rain']] editor on the edit menu ~~(select from main screen in Cumulus 1, or find in the MX browser interface).~~ === (Invented rain) Error in date/time of 'Last Tip' === === (Invented rain) Error in number of consecutive days with or without rain === # The counts are for completed days, not part days. The threshold for whether a day counts as a wet day is set in the optional parameter [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station\|RainDayThreshold= -1]], and the parameter [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station\|NoFlashWetDryDayRecords=1]] is also relevant. # Remember that 'ConsecutiveDryDays' and 'ConsecutiveWetDays' do not include today, they reflect the daily rainfall amounts stored in the [[dayfile.txt\|daily summary log]]. === (Invented rain) Error in total or high rainfall rate for any day before today === Just edit the total or rate for the relevant day in [[Dayfile.txt#Editing_the_file_or_other_Manipulation_outside_Cumulus\|dayfile.txt]], using the [[Cumulus_Screenshots#File.2FEdit.2FHelp_Menu\|the daily summary log file - dayfile.txt]] editor on the Cumulus 1 edit menu ~~(or a suitable external editor that does not add 'BOM' for Cumulus MX)~~. Don't edit the daily summary file close to roll-over time. === (Invented rain) Error in total, or extremes, for this month and/or this year === Longest dry period Longest wet period The correction procedure for all these is as briefly described in [[#How_do_I_correct_my_all-time_.28or_monthly_all-time.29_records.3F \|this FAQ]] and more fully described in [[Correcting_Extremes]]. To see the previous value for all-time records see [[Alltimelog.txt]]. If your all-time records, or month-by-month all-time records have been affected, in Cumulus 1 you can use the built-in editors ~~(in Cumulus MX, use any external text editor)~~. The Cumulus 1 editors can fetch the correct values after you have corrected dayfile.txt. === (Invented rain and) Rain Counter === === (Invented rain) More information === There is more information about correcting rogue data elsewhere in the Wiki, ~~in the pages about the~~see [[~~:Category:Log_Files\|log files~~Correcting_Extremes]]. == My monthly and/or annual rainfall totals are wrong == Cumulus calculates these when it is restarted, holds the values within memory, and increments them as required while it is running. This FAQ in the previous section [[#Where_does_Cumulus_get_its_this_month_and_this_year_rainfall_totals_from.3F]] has a concise description of how Cumulus calculates these figures. ~~{{Version badge 1}}~~ The rainfall total shown on the ''This month'' screen within the '''View''' menu, is calculated from summing [[dayfile.txt]] totals for a selected month, and so for the default current month will exclude the current meteorological day. The rainfall total for today so far is added for the web tag ''<#rmonth>''. If too small a figure is shown, then the most likely issue is that your dayfile.txt is corrupted and Cumulus cannot read one or more lines. Such corruption might be introduced if you have had a power blip while Cumulus was writing to the file, or if you have viewed the file in a Microsoft tool that might have introduced unwanted characters. Both Cumulus 1 and MX provide editors for dayfile.txt, you should use these as they arrange the fields in columns and you should be able to spot when the fields in one line don't match others. The editors for monthly records (and others) have a facility to read dayfile.txt that can pick up some errors in this file and tell you the line number of the first error. The rainfall total for today so far is added for the web tag ''<#rmonth>''. If too small a figure is shown, then the most likely issue is that your dayfile.txt is corrupted and Cumulus cannot read one or more lines. Such corruption might be introduced if you have had a power blip while Cumulus was writing to the file, or if you have viewed the file in a Microsoft tool that might have introduced unwanted characters. The Cumulus editor for [[Amending dayfile\|amending dayfile.txt]] arranges the fields in columns and you should be able to spot when the fields in one line don't match others. The editors for monthly records (and others) have a facility to read dayfile.txt that can pick up some errors in this file and tell you the line number of the first error. ~~{{Version badge 1}}~~The rainfall total shown on the ''This year'' screen within the '''View''' menu, is calculated from summing totals in dayfile.txt for a selected calendar year. For the default current year, it will exclude the current meteorological day. ~~Note that for Cumulus 1 the value labelled "This year" in the rainfall frame may not be the total for this calendar year, as you can choose it to start in any month (see next point).~~ *Note that for Cumulus 1 the value labelled "This year" in the rainfall frame may not be the total for this calendar year, as you can choose it to start in any month (see next point). The rainfall total reported by the ''<#ryear>'' web tag is for the rainfall season to date, it is calculated from taking today's rain and then adding the sum of the totals in dayfile.txt starting with the first (meteorological) day of the month specified in the 'rainfall season' frame on the ''station settings'' screen within the '''Configuration''' menu, until the end of dayfile.txt is reached. So check you have specified the right starting month there before deciding the rainfall total shown is wrong. This is the same figure as is shown on the main screen of Cumulus 1 for "This year" in the rainfall frame. ~~{{Version badge 1}}~~*If you need to, you can specify a year-to-date total to add in for the period up to the point where you started using Cumulus, so that your first year’s total is correct. This is also on the [[Cumulus_Screenshots#Station\|Station Configuration screen]]. Make sure you specify the first Cumulus operating year here, otherwise the extra will be added to the annual total for the wrong year! Do note, if your rain season starts in a month other than January, the extra is added throughout the calendar year specified, it is lost when the season swaps to a different calendar year, and if you change the specified year then it will also apply to the next season! See immediately preceding FAQ [[#My_station_invented_some_rain_that_didn.27t_really_occur.2C_and_I_want_to_set_it_to_zero_.28or_some_other_figure.29 \|correcting rainfall]] for how to correct errors in total for particular days and how to correct the high extremes for the various periods. == I’ve just installed Cumulus, and it didn’t download all the old data from my weather station == ''Cumulus deliberately doesn’t attempt to download any data from before the point when you first run it. ~~If you wish, although this isn~~'t' recommended, you can force it to download data from any point by editing the ‘Timestamp’ line in the [[today.ini]] file (in the data folder), before starting it (you will need to have run it at least once previously). Note that if you do this, it is at your own risk, and you will need to sort out any issues which may arise yourself. {{Version badge 1}} If you wish, although this isn't recommended: # Ensure you have run Cumulus at least once, then stop Cumulus # Edit [[today.ini]] (in the data folder), look for the ‘Timestamp’ line, then carefully sticking to exactly the same format as is currently in the file, change the date and time to your earliest available data in your weather station logger (or just before if you don't know exact time) # Optionally, if you have '''only just started''' using Cumulus, so you have nothing useful to lose, you could delete all of the ''other'' files in the data folder, and delete all lines in the "today.ini" other than those shown in the extract below (with dates modified appropriately). # Now restart Cumulus # if you did step 3, processing will start again with just the data from the station's logger. If#* if you dohave ~~this~~existing files in [[data folder]] when you restart, you will probably need to edit your log files in the '''data''' folder as you may have duplicate entries and/or entries out of order. Your rain totals will almost certainly also be wrong - the total for "today" in particular. See the [[FAQ#My_station_invented_some_rain_that_didn.27t_really_occur.2C_and_I_want_to_set_it_to_zero_.28or_some_other_figure.29 \|FAQ]] entry about correcting rainfall data. If you have only just started using Cumulus, you could delete all of the files in the data folder, and just create a simple today.ini as below. Then when you start Cumulus, processing will start again with just the data from the station's logger.▼ # Note that if you do this, it is at your own risk, and you will need to sort out any issues which may arise yourself. ▲If you do this, you will probably need to edit your log files in the '''data''' folder as you may have duplicate entries and/or entries out of order. Your rain totals will almost certainly also be wrong - the total for "today" in particular. See the [[FAQ#My_station_invented_some_rain_that_didn.27t_really_occur.2C_and_I_want_to_set_it_to_zero_.28or_some_other_figure.29 \|FAQ]] entry about correcting rainfall data. If you have only just started using Cumulus, you could delete all of the files in the data folder, and just create a simple today.ini as below. Then when you start Cumulus, processing will start again with just the data from the station's logger. Note that this method does not work for the Oregon WMR200 station. This station deletes logger entries when they are downloaded, and there is no mechanism for retrieving logger entries for a particular period - it just sends all the entries that it has. You may be able to circumvent this by creating a today.ini file in the data folder before you run Cumulus 1, with just this in it:▼ <pre> [General] CurrentDay=10 </pre> Note that Cumulus MX stores some time-stamps '''in ISO format''' (yyyy/MM/dd HH:mm:ss) within '[[today.ini]]', the format example above only works for Cumulus 1, see the article on the log file itself for specifics. ~~Change the dates and time to match the point from which you want Cumulus to start downloading data. If the station has already sent the data, this may not work, unfortunately.~~ ▲Note that this method does not work for the Oregon WMR200 station. ~~This~~types because this station deletes logger entries when they are downloaded, and there is no mechanism for retrieving logger entries for a particular period - it just sends all the entries that it has. You may be able to circumvent this by missing out step 1 above, and before you run Cumulus 1 for the first time, creating a [[today.ini]] file in the [[data folder]], ~~before~~with just the items shown above in the file. Change the dates and time to match the point from which you ~~run~~want Cumulus 1,to ~~with~~start ~~just~~downloading data. If the station has already sent the data, this inmay not work, unfortunately. ~~it:~~ If you stored data from your weather station (on another file-based system) before you first ran Cumulus, then you may be able to (using a text editor outside Cumulus) generate [[Monthly log files]] for the pre-Cumulus period. See that Wiki article for more information on what you can then do with those files within Cumulus.▼ ▲If you stored data from your weather station (on another file-based system) before you first ran Cumulus, then you may be able to (using a text editor outside Cumulus) generate [[~~Monthly~~Standard_log_files#Importing_pre-Cumulus_data\|standard ~~log~~logging files]] for the pre-Cumulus period. See ~~that~~[[Calculate ~~Wiki~~Missing ~~article~~Values\|elsewhere in this Wiki]] for more information on what you can then do with those files within Cumulus. == I have inserted pre-Cumulus data and now I get errors == Probably some of your inserts used the wrong format (blank rows, fields with real numbers where integers expected, alternatively missing or duplicated fields). See [[:Category:~~Log_Files~~Files with Comma Separated Values]]. Note that Cumulus 1 will only flag errors in the log files that it reads (e.g. those relating to the period for which it displays trends graphs). Check all the log files you have amended. == I have inserted pre-Cumulus data making ''''Records began on' ~~date~~this_date''' wrong == ~~Stop~~'''You ~~Cumulus~~do NOT need to change ~~and~~anything ~~edit~~in [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station \| ~~Cumulus.ini (~~'''station''' section) of cumulus.ini]] ~~within the main~~for Cumulus ~~folder.~~1 ~~Change~~to ~~the~~recognise ~~"StartDate="~~earlier ~~line.~~data Bein ~~sure~~log tofiles ~~use~~in ~~the~~its ~~same~~[[Data ~~format~~folder\|''data'' ~~for the date.~~subfolder]]''' There might be confusion about the terminology ''Records'', in the Cumulus usage it does not mean when was your earliest data, it means when did Cumulus start tracking extremes (see [[Correcting_Extremes#Introduction]] (it does not say '''Data recording began on'''). You should update the extreme records for the inserted data, as advised in [[Correcting_Extremes]] before you make the changes suggested below. ~~{{Version badge 1}}'''Note''' ''StartDate=xxxx'' does ''not'' need to be updated for Cumulus 1 to recognise earlier data in log files in its ''data'' subfolder.~~ ''''Records began on' this_date''' appears in TWO places in the example [[Cumulus_template_file\|template file]] called [[Customised_templates#The_Standard_Templates_for_Cumulus_1\|recordT.htm]]: [[File:Badge vMx.png]] However in calculating and updating extremes, Cumulus MX will ignore any monthly log file data prior to the start date set, so it is crucial to make sure the start date is right before you (re-)start MX. #after the h2 heading is ''<p>Records began on <#recordsbegandate>. Here are the extremes recorded since then.</p>''; ~~you can replace '<#recordsbegandate>' with the new earliest date typed in as text; and~~▼ #at the start of the table is the ''<caption>Records Since <#recordsbegandate></caption>''; ~~replace the label "Records since" with "Cumulus began on" leaving the web tag unchanged.~~▼ There are alternative ways to correct this (do any one or any combination): You can manually replace the '''<#recordsbegandate>''', with any date as ordinary text, in either or both of those places. You can manually replace either ''Records began on'' or ''Records Since'' with '''Cumulus began on''' leaving the web tag unchanged. *You can change the other one, not changed above, to read '''Imported data starts''' and replace the web tag with the new date. You can stop Cumulus, and manually edit [[Cumulus.ini_(Cumulus_1)#Section:_Station \|'''station''' section of cumulus.ini]] within the main Cumulus folder. *Change the "StartDate=" line so the value for that property has the date you want. Be sure to use the same format for the date. Like most FAQ on this page, this was written for Cumulus 1, please be aware that MX works differently, and so this does not apply! ~~{{Version badge 1}}It really represents "Cumulus began on", so there is an alternative of leaving cumulus.ini unchanged, but editing default Cumulus ''recordsT.htm'' template twice:~~ ▲after the h2 heading is ''<p>Records began on <#recordsbegandate>. Here are the extremes recorded since then.</p>''; you can replace '<#recordsbegandate>' with the new earliest date typed in as text; and ▲at the start of the table is the ''<caption>Records Since <#recordsbegandate></caption>''; replace the label "Records since" with "Cumulus began on" leaving the web tag unchanged. == Cumulus doesn’t show the same pressure as my Fine Offset console == # that you are comparing the Cumulus display with the ‘relative’ pressure on your console, # that only one copy of Cumulus is accessing the weather station (and no other software), # that you do not have a 'EWpressureoffset=x.y' line in the [Station] section of [[Cumulus.~~ini~~ini_(Cumulus_1)#Introduced_for_problems_with_Fine_Offset_family:\| cumulus.ini]], # and that you do not have a setting for pressure on the Cumulus calibration screen. The Fine Offset stations only store absolute/station pressure readings in their weather memory locations updated with each transmission and read by Cumulus. Within Cumulus, the software applies the adjustment to sea level before any further processing. It does ''not'' use the altitude setting in the cumulus station configuration screen. Normally when Cumulus starts, it reads in [http://www.jim-easterbrook.me.uk/weather/mm/ the fixed block] in the console a pair of absolute/station pressure and relative/sea level pressure readings and uses the difference between these as the ‘offset’ in millibar for the station; Cumulus uses this offset subsequently to calculate the sea level pressure (each time when reading the absolute pressure in the weather memory locations of the station), but it is possible to define the offset in '''Cumulus.~~ini~~ini_(Cumulus_1)''' instead. ~~{{Version badge 1}}~~'''IMPORTANT''' These notes apply to Cumulus 1. '''bvs79669''' did some investigation in January 2019 that reveals ~~the~~ ''the [[Fineoffset_Memory_Map\|mapping of memory bytes to pressure]], reported by Jim Easterbrook, and used by Steve Loft is wrong''. The two most significant bits included in that mapping as being part of the pressure output should not be included as they create impossibly high readings for pressure. ~~From build 3047, MX excludes these two bits when reading the pressure and the reliability of reading correct pressure from a Fine Offset station has been significantly improved.~~ Make sure that you have set your console's relative pressure correctly: EWpressureoffset=x.y where x.y is your pressure offset. '''Cumulus will then use this instead of reading the fixed block offset from the station'''. '''Note''' that ''you must supply the offset in hPa'' (i.e. the millibar units that the station works with) and that this circumvention generally stops Cumulus from agreeing with the relative pressure displayed on the console. ~~''If you swap from Cumulus 1 to Cumulus MX, remove this pressure offset'', MX is much better at communicating with the weather station and rarely needs use of this offset.~~ ''If you swap from Cumulus 1 to Cumulus MX, remove this pressure offset'', the latest release of MX is much better at communicating with a Fine Offset weather station and rarely needs use of this offset. == My pressure suddenly dropped! Or suddenly increased! == == I get an error when I try to view my all-time records. Also, they don’t appear on my web site == The date format on your system has probably changed. If you look at [[Alltime.ini\|alltime.ini]], you may spot the date format differences and work out what was date of change. Otherwise, go into '''Control Panel''' on your PC (not "Settings" as is normal for Windows 10 Operating system) and open the '''Clock and Region''' section. Next choose '''Region''' option. On the "Region pop-up-screen" you should check what is shown in the ''Format'' box, and what is shown in ''Short date'' and ''Long date'' drop downs. The date format on your system has probably changed. Look at the Startdate line in cumulus.ini and check whether this is in the correct format for your system. If not, stop Cumulus and correct the date format. Please see [[Correcting_Extremes]] page for further advice. == I get an error when I close Cumulus == ~~{{Version badge 1}}~~ Cumulus 1 does sometimes report an error when you close it. This does not appear to cause any problems, you can just close the error message. I don't seem to be able to do anything about this, as the 'crash' is not in code that I have control over. You may be able to avoid this error by avoiding closing Cumulus while it is uploading to the internet. Please don't bother sending me a bug report about this. == My forecast says "Not available" == == When I start Cumulus, the graphs restart again each time and don't show the earlier data == {{Version badge 1}}You probably have an error in one or more data files. Look near the beginning of the latest file in the ~~Diags~~ [[Diags_folder\|sub-folder called 'diags']] for an error message which will tell you which file is in error and which line is causing the problem. It may simply be a blank line. Edit the file with Cumulus stopped. Note that you may need to repeat this process; only the first error is shown. This problem can also occur if you change your system format settings (date format, decimal and list separators etc). Again, check the diags file for a message about a number not being a valid floating point value. The most likely explanation is that you have only recently started running Cumulus (in the last day or two). It adds new values to this graph at the end of each day; it wouldn't make sense to add a value part of the way through the day, and you need a few points to be plotted before the graph starts to take shape. You need to wait until you have been running Cumulus for a few days. If you've been running Cumulus for more than a few days, but the graph is still empty, the most likely explanation is that it was unable to read your dayfile.txt file. Look at the latest file in the [[Diags_folder\|'diags']] folder (the files are plain text) for error messages mentioning dayfile.txt. == The longest dry/wet spell for this month/year includes days from last month/year == This is an attempt to make sure that bad data is not logged. If your weather station is not fully functional, you will not be able to use Cumulus fully. You can over-ride the start up check by adding a line to the [Station] section of [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_Station\|cumulus.ini]], thus: ''NoSensorCheck=1'' (You need to do this while Cumulus is stopped). Note that you are likely to get bad data logged if you do this. '''NOTE: In Cumulus MX, you can now set the No Sensor Check value from the GUI. See... Station Settings \| Common Options''' == I've changed my Twitter password, and now Cumulus won't update Twitter == # start Cumulus up again. '''Today's''' totals, highs and lows (and '''yesterday's rain''' total) are held in [[today.ini]] in the Cumulus data folder. Follow the cross-references if you are unsure which parameter is what. To change any values, stop Cumulus and edit the file(s) in a text editor. Be sure to keep any date and time formats the same ~~(they vary between Cumulus 1 and MX)~~. If you are editing '''yesterday's highs and lows''', the totals (including RG11 rain but not standard rain), highs, and lows are held in [[yesterday.ini]]. However, you probably also need to ~~edit~~read [[~~Dayfile.txt#Editing_daily_summary_in_Cumulus\|dayfile.txt~~Amending_dayfile]], as many of the values should have been written to ~~that file~~[[dayfile. ~~Both flavours of Cumulus (1 and MX) have log~~txt]] file ~~editors, be sure to us the right editor for the type of log file you are editing~~. If your all-time and/or monthly all-time records have been affected, see the next [[#How_do_I_correct_my_all-time_.28or_monthly_all-time.29_records.3F\|FAQ entry]]. == How do I correct my all-time (or monthly all-time) records? == Cumulus works by whenever the reading it is currently processing exceeds a particular record, that record is updated. In essence, Cumulus end-of-day works by reading what is in the monthly [[Standard_log_files]] to find the highs and lows during the day just ended, these then update the [[dayfile.txt\|daily summary log]]. Cumulus can also read what is in the daily summary log to update the all-time extremes held in [[alltime.ini]] and month-by-month all-time extremes held in [[monthlyalltime.ini]]. Look up those cross-references to help you understand the various items, and how they can be updated. Cumulus works by whenever the reading it is currently processing exceeds a particular extreme record, that record is updated. It cannot make any adjustments retrospectively. ~~Either 1) Consequently, you can manually copy the sequence remembering it requires several steps:~~ # Correct the rogue values or values in the monthly [[Standard_log_files]] ''with Cumulus stopped''. Neither Cumulus 1 nor Cumulus MX provides an editor to do this, and you need to guess new values for readings as there is no other file provided by Cumulus to offer any suggestions, often people interpolate between earlier and later readings. # Correct the [[dayfile.txt\|daily summary log]] ''(don't do this near the rollover time)'', the editor in Cumulus 1 requires you to manually change the numbers, unless you delete the whole day (or it was previously missing) and you ask Cumulus to '''Insert missing''' i.e. populate a single line (day) from the detailed log, ignoring any extremes at times between logged readings. # Correct the all-time extremes held in [[alltime.ini]] and monthly all-time extremes held in [[monthlyalltime.ini]]. Using the Cumulus 1 [[Cumulus_Screenshots#File.2FEdit.2FHelp_Menu\|built-in appropriate editor]] from the first couple of commands in the Edit menu (and now also in CumulusMX) allows you to see, and copy across, suggested extremes based on contents of the monthly [[Standard_log_files]] or contents of the [[dayfile.txt\|daily summary log]].▼ ~~or 3)~~ Cumulus takes a backup of most of the active data files when it starts up, and also at the start of the meteorological day (just after midnight for a lot of users). The backups are kept in folders within the backup sub-folder in the Cumulus installation. So ~~yet~~often ~~another~~the ~~alternative~~easiest method would be to find the latest backup from before the error occurred, and copy the ''alltime.txt'' and/or ''monthlyalltime.txt'' file from the backup to the Cumulus data folder. Do this with Cumulus stopped~~. There is more information in [[:Category:Log_Files]], for all of the types of file~~.▼ or 2) If you know the correct figures, you can alternatively enter them manually directly into the .ini files and not bother to update the detailed log or the daily summary log. (It is pointless to edit the .ini files directly and then afterwards edit the log files):▼ You can look at the [[Alltimelog.txt]] file to find the previous values for the [[alltime.ini\|all-time records]].▼ Similar entries are logged to the [[diags]] files for any updates to the monthly highs and lows in [[monthlyalltime.ini\|month-by-month records]]. ▼ ▲#There ~~Correct~~is ~~the~~advice ~~all-time extremes held in~~on [[~~alltime.ini~~Correcting_Extremes]] ~~and~~page ~~monthly~~that ~~all-time~~explains ~~extremes~~how ~~held~~corrections incan ~~[[monthlyalltime.ini]]~~be made. Using the Cumulus 1 [[Cumulus_Screenshots#File.2FEdit.2FHelp_Menu\|built-in appropriate editor]] from the first couple of commands in the Edit menu ~~(and now also in CumulusMX)~~ allows you to see, and copy across, suggested extremes based on contents of the monthly [[Standard_log_files]] or contents of the [[dayfile.txt\|daily summary log]]. ▲~~or 2)~~ If you know the correct figures, you can alternatively enter them manually directly into the .ini files and not bother to update the detailed log or the daily summary log. (It is pointless to edit the .ini files directly and then afterwards edit the log files): ▲or 3) Cumulus takes a backup of most of the active data files when it starts up, and also at the start of the meteorological day (just after midnight for a lot of users). The backups are kept in folders within the backup sub-folder in the Cumulus installation. So yet another alternative method would be to find the latest backup from before the error occurred, and copy the ''alltime.txt'' and/or ''monthlyalltime.txt'' file from the backup to the Cumulus data folder. Do this with Cumulus stopped. There is more information in [[:Category:Log_Files]], for all of the types of file. ▲You can look at the [[Alltimelog.txt]] file to find the previous values for the [[alltime.ini\|all-time records]]. ▲Similar entries are logged to the [[Diags_folder\|sub-folder called 'diags']] files for any updates to the monthly highs and lows in [[monthlyalltime.ini\|month-by-month records]]. == It's January 1st and my 'rain since midnight' and/or 'last 24 hours rain' and/or Evapotranspiration are wrong/negative == If you look in the status bar at the bottom of the Cumulus window, there may a message "Error: no response"; this would confirm that the station has locked up and needs resetting. If you are using the "Synchronise" setting but are still getting frequent console interface lockups, then the clocks on the console and the platform running Cumulus may be drifting too far between synchronisations. Look in the ~~diags~~[[diags_folder]] files for the word "drift" and see how many seconds apart the clocks are drifting. If it is more than 3 seconds, you will need to adjust the period that Cumulus allows where it doesn't read the console data. Stop Cumulus and edit Cumulus.~~ini~~ini_(Cumulus_1). In the [Station] section, add a line: FOReadAvoidPeriod=N {{Version badge 1}}See this forum post - https://cumulus.hosiene.co.uk/viewtopic.php?f=2&t=14148 == How do I enable debug logging in ~~CumulusMX~~Cumulus? == ~~There are a number of ways of enabling logging~~ This depends on your build: From b3068 CumulusMX can be started with the -debug parameter to switch on debug and data logging from start-up. This is often the best option. * The only way to turn on the logging of debugging messages in all builds of Cumulus 1, is to stop Cumulus 1, edit the [[Cumulus.ini_(Cumulus_1)#Section:_Station\|Cumulus.ini_(Cumulus_1) configuration file]], and add a line in the [Station] section: <tt>Logging = 1</tt>, then restart Cumulus 1. Whilst MX is running the logging can be switched off/on via the administrator interface - Settings\|Station settings\|Options ''Debug logging'' & ''Data logging'' From build 1003 onwards, you can also turn it on/off using the '''Configuration''' menu (debug option is included in drop down of that menu). With MX stopped, edit Cumulus.ini. In the [Station] section set (or add if missing) the two entries... ~~<pre>Logging=1~~ Please see all these pages: [[Bugreport.txt]], [[Debug.log]], and [[Diags_folder]]. ~~DataLogging=1</pre>~~ = Website = == How do I replace the 'bird' image on my website? == There are several ways to change the image of the 'bird' on the standard Cumulus web page. You will need a [[FTP tools\|FTP tool]]. The simplest way is to upload a new picture to the images folder of your website; the file should be called picture.jpg. Please ensure the image is not too large and bear in mind it will appear on the bottom left of the page; the site data may cover some of the image. As a guide, the default image is 600 x 450 pixels. * Secondly, you may upload an image using your own file name. Edit the ''weatherstyle.css'' file and look for the line <tt>background-image: url(images/picture.jpg);</tt> around line 9 and adjust as necessary. Upload the edited css file to your website. <td></td> </pre> If you want to stop Cumulus uploading the indoor temperature graph, you can un-tick 'Include standard images' on the 'files' tab of the internet settings, and list all of the images that you still want to be uploaded as extra files. Cumulus 1 configuration only allows you to add 10 files so you would need to do this by editing Cumulus.~~ini~~ini_(Cumulus_1), ironically these notes do not apply to Cumulus MX but in that all 100 slots can be edited within the settings pages. To show solar instead, replace 'intemp.png' with 'solar.png', replace 'intempsm.png' with 'solarsm.png', and change the wording of the value associated with the alt property. To make Cumulus upload the solar graph, select it on the 'files' tab of the internet settings. Deselect the option where indicated by red arrow if your template includes something like <code><meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type" /></code> For customised pages, (without standard Cumulus template names), select/un-select the UTF-8 encoding in the appropriate column on the '''Configuration''' menu, ''Internet'' dialog, '''Files''' tab screen where you list the local and remote names. Or you have edited/customised the template and added an incorrectly specified Cumulus [[~~webtag~~webtags]] that has caused [[Customised_templates#What_is_meant_by_.27Cumulus_processes_templates.27\| Cumulus processing]] to abort for that template. If you stop cumulus you can use a text editor to open the latest [[~~Diags~~Diags_folder\|diagnostic file]]. Look at entries time-stamped just before the hour and repeated at your auto-update ''interval'' (just below red arrow in screen image above). You might find a message like "Error processing C:\web\indexT" (i.e. mentioning whichever template is at fault) followed by a brief hint as to the nature of the error. == My web pages have obsolete web tag values in them == You'll need to list the (source) file including paths on the files tab of the internet settings, and specify a destination path and file name for the remote file in each case. Don't tick the ''FTP?'' box for standard cumulus pages (the exception is for a local web server and any non-standard web page that attempts to read using a script a local file such as dayfile.txt as this does need FTP to generate the server-based web page). For the standard images, you can supply a folder name (specify on the same screen), and they will all get copied there. See [[Customised_templates#What_to_select_on_the_.27Files.27_tab_of_the_Internet_Settings_screen_within_the_.27Configuration.27_menu\|here]] for greater detail. There's a limit of 10 entries on the files tab in Cumulus 1.9.x (in Cumulus MX all 100 entries are included in the settings interface). Entries for the full 100 files can also be amended by editing [[Cumulus.~~ini~~ini_(Cumulus_1)#Section:_FTP_site\|cumulus.ini]], with Cumulus stopped. Follow the format of any existing entries for specifying additional files. == Error Codes generated by FTP or Winsock == Cumulus 1 doesn't support Secure FTP. You can configure Cumulus to invoke an external program like WinSCP, as described here: [[SFTP \| SFTP article]] ~~Cumulus MX supports FTPS (FTP over TLS) natively, but not SFTP. Just enable it in the settings.~~ == Directory related problems in FTP == * ~~IN CUMULUS 1.x.y ONLY:~~ The ''standard pages'' are uploaded after a 'change directory' attempting to select the directory you specified in '''Sites/Options'''; if this fails, the files will still be uploaded but to the FTP server root. So some mistakes do not matter because if no change of directory was actually required, these pages will be uploaded correctly. * IN CUMULUS MX, the ''standard pages'' are uploaded with their file name prefixed by the directory you specified in '''Sites/Options'''. In this case, if that path is invalid, the upload fails. * Any ''files you specify'' for uploading at standard update frequency are uploaded between standard pages (if 'Include Standard Files' selected) and (applies only to Cumulus 1) standard images (if 'Include Standard Images' selected). You should specify the path (including any web site directory) in 'remote filenames', as there is no call to 'change directory'. In this case, if that path is invalid, the upload fails. * ~~IN CUMULUS 1.x.y ONLY:~~ The standard images for gauges and trends pages are uploaded after the standard pages, (and any pages you specify for uploading), by performing a second 'change directory' this time fixed at 'images'; if this fails, the files will still be uploaded to the current web site directory (FTP root or the directory you specified in '''Sites/Options'''). * If you have enabled ''Realtime'', the realtime.txt file is uploaded without doing a change directory, (by appending "/realtime.txt" to the directory on the ''Internet settings'' screen in '''Sites/Options'''). In this case, if the web site directory in your settings is invalid, the upload of the real time file fails. * On the ''NOAA Setup'' screen the optional '''Directory''' parameter required is the relative path; from your FTP root, to where the NOAA report pages are to be stored. (It is totally independent of the directory on the ''Internet settings'' screen in '''Sites/Options'''). Click the '''Help''' button for full explanation. Like realtime.txt, the upload destination is determined by appending the file-name for the report to any NOAA directory, and will fail if that directory is specified wrongly.