nyuuzyou/wikis huggingface dataset:
HeavyWeather

= La Crosse weather stations =
The software used with the device is Heavy Weather, and while it peforms its role of reading, displaying, and storing data from the weather station, Heavy Weather Software is quite limiting and inflexible. Of course, if you are reading this you have probably already switched to Cumulus and found its advantages.
Using the Heavy Weather program, you can open the History window and save the weather data from the desired history file as a text file ready to import any pre-Cumulus observations. See Monthly_log_files or EasyWeather_Format for more inspirational tips on such imports. During normal running, HeavyWeather software outputs to a file called history.dat, but each of these holds only a limited number of records. La Crosse also offer Pro Weather Station Software to analyse the output of Heavy Weather.
Category:StationSpecific
Help System

= Introduction =
CumulusUtils has a help system for the Charts (through the ChartsCompiler) and for the Climate Charts (Graphs menu choice). 
For the website viewer there is no difference: the small word info appears left of the hamburger menu in the chart and when clicked there is some Help info available through a popup modal window. If it is not available, the word Info won't appear.
For the owner of the Website is the task to write some information which makes the charts more clear for the viewer.
= Operation =
Technically there are currently two systems:
# The charts generated through the ChartsCompiler have the keyword Info in CDL
# The charts in the menu Graphs assemble the Info text from the file CUhelptexts.txt where the website owner has his help texts.
The CutilsCharts.def for the ChartsCompiler is described on the ChartsCompiler page.
The CUhelptexts.txt file resides in the utils directory an will be created when it does not exist: run CumulusUtils once without an argument. It has the following default content:
 HT_DailyRain = " "
 HT_MonthlyRain = " "
 HT_YearlyRainStats = " "
 HT_YearlyMonthlyRainStats = " "
 HT_MonthlyTemp = " "
 HT_YearlyTempStats = " "
 HT_YearlyMonthlyTempStats = " "
 HT_WarmerDays = " "
 HT_HeatMap = " "
 HT_WindRose = " "
 HT_WindRun = " "
 HT_YearlySolarHRSstats = " "
 HT_YearlyMonthlySolarHRSstats = " "
 HT_YearlyInsolationStats = " "
 HT_YearlyMonthlyInsolationStats = " "
 HT_TempSum = " "
 HT_GrowingDegreeDays = " "
 HT_ThermalSeasons = " "
 HT_DailyEVT = " "
 HT_MonthlyEVT = " "
 HT_ClashOfAverages = " "
The structure is <tag> = " <free text> " ; The spaces are obligatory, the tag names are fixed and must not be changed by the user.
The spaces are obligatory for the parser to recognize the structure of the file and a space between the double quote and the free text between the quotes is also obligatory. The user can write any HTML formatted text between the quotes, in principle of any length (though some restraint is advisable). 
All climate graphs have their own meaningful entry - e.g. HT_DailyRain means Help Text for the Daily Rain chart - and can have their own text. If no text is specified (only white space between the double quotes) the Info word will not appear in the chart.
= Output =
The helptexts are assembled in the different charts files (e.g. graphsrain.txt and cumuluscharts.txt).
= Inifile parameters = 
There are no inifile parameters related to this helptext information system
= Other remarks =
The Info keyword in the ChartsCompiler will eventually be unified with the CUhelptexts.txt file system when an unambiguous merge can be constructed.
When errors have been made or the default tag names have been changed and the system no longer works, just remove the CUhelptexts.txt file and rerun CumulusUtils without argument.
Category:CumulusUtils
Highcharts - Realtime

= Dynamically Updating a Highcharts Graph from Realtime.txt =
This page describes how to implement a simple dynamically updating chart using Highcharts, PHP, realtime.txt, and AJAX. 
= Requirements =
The web server must have.. 
*PHP 
*Cumulus Realtime.txt
= Installation =
*Download and copy the Highcharts files on to your web server 
*Download the GNU utilities for Win32 - I used the latest updates (after 14-04-03)  
*Download the Realtime_Highcharts ZIP file  (right click, Save as)
Next you have to decide where and how the realtime log file will be created. The zip file contains a simple Windows batch file that will create a log file of a specified length. If you have a Windows web server you could run it directly on there (this is how I do it), or run it on your Cumulus computer and get Cumulus to upload the log file periodically. 
Wherever you run the batch file to create the realtime log, you will also need a copy the 'tail.exe' utility from the GNU utilities for Win32 zip file. 
Alternatively Kevin at TNET Weather has created a PHP script to create such a log file. The batch file is simple and creates a limited length log file, the TNET scripts typically create much larger log files.
A third alternative is to use Cumulus Toolbox, which has the option to create a realtimelog.txt in your Cumulus folder, You can then use Toolbox to copy of FTP this file to your web server. Toolbox has has the option to 'prune' the logfile, with a granularity of 1 day.
= The result =
You should end up with a default graph looking something like this Image:RealtimeHigharts.JPG 
= Configuring the graph =
For consistency, the graphed data ranges are all referred to by their equivalent Cumulus webtag names. 
The supplied files are configured to display the current rainfall, atmospheric pressure, average wind speed, and temperature. If you want to change this there are three areas of the realtimeCumulus.js file that will require editing: 
*parseRealtime function: Change or amend each of the "chart.series[].addPoint()" lines. The order here must match the options.series changes below... 
*options.yAxis object: Change or amend each yAxis scale to match your desired data series. 
*options.series array: Change or amend each data series to match your desired data series. Note the reference back to the corresponding yAxis number. 
*$.ajax url: Change or amend the required data series in the url construction.
= What next? =
That is left as an exercise for you :), maybe include this in an AJAX enabled 'Conditions now' page - similar to the supplied Cumulus index.htm? This is what I have done here.
The realtimeLogParser.php can also be used for any other purpose you like too ;)
= Version Control =
*1.0 - 29 Nov 2012 - First release [Download]
Category:WebToolsCategory:User Contributions
Instromet

== General Points ==
This page is an attempt to summarise some of the information specific to Instromet stations that is elsewhere in this Wiki; for more information search within answers on the Cumulus support forum.
== Cumulus Version to use ==
Instromet stations using Cumulus 1 should install the latest build specified here.
The latest MX version can be seen at top of every support forum page.
== Extra Sensors ==
See here for settings and here for specifics.
Category:StationSpecific
Italiano (Italian)

Although Cumulus does not directly support languages other than English, the standard web templates have been translated where possible into Italian.
=Installation=
*Download and unzip this file.... https://cumuluswiki.org/files/IT-web.zip
*There will be seven files extracted. Copy the six files ending '.htm' and replace the files in your Cumulus 'web' folder. 
*If you are using Cumulus version 1.8.8 build 871 or higher you may also use the strings.ini file included in this zip and place it within your Cumulus application folder. This file includes translations for all the forecast and moon phases.
*The next time Cumulus performs a web update your site will be in Italian.
*An alternative set of files is available, which also includes the web pages added in later versions of Cumulus... https://cumuluswiki.org/files/IT-web2.zip
=Version Control=
*1.0 First release
Category:Other Languages
Lunar phase

Lunar phases (or Phases of the Moon) are the result of looking at the illuminated half of the Moon from different viewing geometries; they are not caused by shadows of the Earth -- this would be a lunar eclipse. The Moon exhibits different phases as the relative geometry of the Sun, Earth and Moon change, appearing as a full moon when the Sun and Moon are on opposite sides of the Earth, and as a new moon (also named dark moon, as it is not visible at night) when they are on the same side.
=Names of lunar phases=
The phases of the Moon have been given the following names, in sequential order:
Phase 	Northern Hemisphere 	Southern Hemisphere 	Visibility 	
New moon 	Not visible, or traditionally, the first visible crescent of the Moon	 	 	
Waxing Crescent moon .	Right 1-49% visible 	Left 1-49% visible 	afternoon and post-dusk 	
First Quarter Moon 	Right 50% visible 	Left 50% visible 	most of the day and early night	
Waxing gibbous moon 	Right 51-99% visible 	Left 51-99% visible 	afternoon and most of night 	
Full Moon 	Fully visible 	Fully visible 	sunset to sunrise (all night) 	
Waning gibbous Moon 	Left 51-99% visible 	Right 51-99% visible	most of night and morning 	
Last Quarter Moon 	Left 50% visible 	Right 50% visible 	late night and most of the day 	
Waning Crescent Moon 	Left 1-49% visible 	Right 1-49% visible 	pre-dawn and morning 	
Darkened moon 	Not visible 	Not visible 	 	
The average calendrical month, which is 1/12 of a year, is about 30.4 days, while the Moon's phase (synodic) cycle repeats every 29.53 days. Therefore the timing of the Moon's phases shifts by an average of about one day for each successive month
=Cumulus Webtag=
Cumulus has three webtags relating the phase of the Moon.
Cumulus processes a <#moonphase> representing the current phase of the Moon. By default, as these can be modified, one of the following eight strings will be returned:
*New moon
*Waxing Crescent
*First Quarter
*Waxing Gibbous
*Full moon
*Waning Gibbous
*Last Quarter
*Waning Crescent
These default values can be overridden by editing the Strings.ini file.
Cumulus also has two webtags relating to the percentage illumination of the Moon.
<#MoonPercent> returns the percentage of the visible surface illuminated, with positive values for a waxing Moon and negative values for a waning Moon.
<#MoonPercentAbs> returns the percentage of the visible surface illuminated, and is always positive.
Category:Terminology
Modules

== Introduction ==
Modules are the basic building blocks of CumulusUtils. Identifying modules on the commandline they become synonym with commands to CumulusUtils and can be used in a users own website. The website is not seen as a module but it is the CUtils own aggregate of the modules.
== The list of modules ==
CumulusUtils offers the following modules (which can be used as commands):
#SysInfo
#pwsFWI
#ExtraSensors
#Custom Logs
#Graphs
#Yadr
#Records
#NOAA
#Forecast
#StationMap
#UserReports
#Top10
#DayRecords
#AirLink (before version 6.1 this was AirQuality)
#ChartsCompiler
#MeteoCam
#Diary
#UserAskedData
== The multiple module commands ==
In addition to the true modules which are equivalent to commands, there are commands which are strictly spoken not modules because they do not comprise a single functionality:
#Website => generates the website which consists of all modules, the inclusion of the libraries is embedded in website's index.html.
#UserAskedData => a specific command used for generating JSON datafiles when required by other modules (e.g. AirLink, Extra Sensors and CustomLogs)
#CompileOnly => a command which activates the compiler only. This is a very specific command with more than one effect. Please check out its own page.
If you use modules but want the resulting server location outside of your main website location (e.g. in a subdirectory CUtils) then please create that directory and set your uploads for CUtils accordingly. To have your website find the specific realtime values (the JSON files) specifically generated for CUtils, than run the UserAskedData command and set the parameter where to locate those data. In the case as above:
 DoModular=true
 ModulePath=<path>
DoModular and the command Website are incompatibe
== Javascript libraries ==
When using the Website Generator, all modules are used implicitly. Modules, with some exceptions, can be used standalone in any website by including the output of CumulusUtils in that website. When using the standalone mode you need to be aware of the inifile parameters (section general) GeneratejQueryInclude and DoLibraryIncludes.
#GeneratejQueryInclude will - if true - generate the required jQuery library reference line on top of the module.
#DoLibraryIncludes will - if true - generate the required library references (e.g. HighCharts, Leaflet etc...) on top of the module.
If you manage these libraries in your website yourself set these parameter values to false.
If the modules don't work and you have no idea what this is about, set these values to true.
If you use the Website Generator, set both parameters to false.
== Commandline parameters (v7 and up) ==
To have modules work properly with the commandline parameters introduced in version 7 of CUtils, you need to use the runtime library for CumulusUtils
 <script src='lib/cumulusutils.js'></script>
This library is generated with the website command separately with the CUlib command. 
It has it's own entry in the wiki.
You can also use - i.s.o. the library above - a script in your own HTML file:
 <script>
 const urlParams = new URLSearchParams(window.location.search);
 </script>
Category:CumulusUtils
NOAA

== Introduction ==
CumulusUtils provides a possibility to display the NOAA reports generated by CumulusMX by choosing year and month from a menu. The current month in the current year is where the display starts. This module assumes only the CumulusMX default settings for the filenames are valid.
== Operation ==
This module is included in the website. When needed as a single output the following command is given: 
 utils/bin/cumulusutils.exe NOAA
== Output ==
The output is a file named noaa.txt
== Inifile parameters ==
 [NOAA]
 FTPDirectory=./reports/
 ColorNOAAText=Black
 ColorNOAABackground=#f9f8EB
 StartInCurrentMonth=true
== Inner working ==
Through the menu the year and month is selected and from those values the report filename is constructed and displayed. If StartInCurrentMonth is true the month report of the current month is displayed otherwise the year report of the current year is shown. The colours and the formatting of the reports is taken from a beteljuice formatting which wandered around somewhere. The colours can be changed.
The directory where the reports can be found must be the directory where CumulusMX stores the reports, check if initial capital required. 
The first thing you need to check is whether the reports are actually copied to the website by CMX because that is the most important thing. In CMX you define a directory and CMX copies the reports there. If that is not the case you must work in CMX until that is the case.
Then, once the reports are on the website directory somewhere in or below the webroot, you should be able to view them in the CumulusUtils website. In the NOAA section of the CumulusUtils inifile you find a parameter FTPDirectory which is where CMX stores the reports. It actually must be the relative location to the webroot. So if your directory by CMX is /public_html/reports/ (FTP directory) in Cutils that becomes: ./reports/ because - sorry for this confusion which exists for historic reasons - in Cutils the reports are actually fetched in HTML context which means it starts from the webroot.
Category:CumulusUtils
Nederlandse (Dutch)

file:flag_Netherlands.GIF Although Cumulus does not directly support languages other than English, the standard web templates have been translated where possible into Dutch.
Many thanks to Gerard van 't Klooster and 'Nitrx' for their work on the translation.
=Installation=
*Download and unzip this file....https://cumuluswiki.org/files/NL-web.zip
*There will be seven files extracted. Copy the six files ending '.htm' and replace the files in your Cumulus 'web' folder. 
*If you are using Cumulus version 1.8.8 build 871 or higher you may also use the strings.ini file included in this zip and place it within your Cumulus application folder. This file includes translations for all the forecast and moon phases.
*The next time Cumulus performs a web update your site will be in Dutch.
Warning: If you upgrade your version of Cumulus these files will be replaced with the standard files so you will need to repeat the above process. If you make any customisation to these please take a backup before upgrading otherwise you will have lost your work.
=Example=
A static example is currently available here
=Version Control=
*1.2 Added strings.ini translation
*1.1 Fix to 'trends' page, use of 'average' and 'Daily rainfall' labels now translates 
*1.0 First release
Category:Other Languages
Norsk (Norwegian)

Although Cumulus does not directly support languages other than English, the standard web templates have been translated where possible into Norwegian.
Thank you to 'grottem' on the Cumulus forum for his assistance in the translation.
=Installation=
*Download and unzip this file.... https://cumuluswiki.org/files/NO-web.zip
*There will be seven files extracted. Copy the six files ending '.htm' and replace the files in your Cumulus 'web' folder. 
*If you are using Cumulus version 1.8.8 build 871 or higher you may also use the strings.ini file included in this zip and place it within your Cumulus application folder. This file includes translations for all the forecast and moon phases.
*The next time Cumulus performs a web update your site will be in Norwegian.
Warning: If you upgrade your version of Cumulus these files will be replaced with the standard files so you will need to repeat the above process. If you make any customisation to these please take a backup before upgrading otherwise you will have lost your work.
=Example=
A example is not currently available
=Version Control=
*1.1 Update to strings.ini with better Norwegian phrases
*1.0 First public release
Category:Other Languages
Pop-Up Graphs - Gauges Page

== Introduction. ==
This page attempts to describe step by step how to setup the Pop-up Graphs that can be seen on the Gauges pages when hovering the mouse over a particular gauge.
Theses are more correctly referred to as Server Generated Graphs, as they are created on the Web Hosting Server.
There is a lot of detail in this thread in the forum, which now spans 6 years.
=== Basic Overview. ===
Re-Visiting this during a Hosting Migration.
Requirements:-
JpGraph, from here...
https://jpgraph.net/download/
Cumulus-MX-Gauge-Graphs, from here...
https://github.com/mcrossley/Cumulus-MX-Gauge-Graphs
Portuguesa (Portuguese)

Although Cumulus does not directly support languages other than English, the standard web templates have been translated where possible into Portuguese.
=Installation=
*Close down Cumulus
*Download and unzip this file.... https://cumuluswiki.org/files/PT-web.zip
*There will be seven files extracted. Copy the six files ending '.htm' and replace the files in your Cumulus 'web' folder. 
*If you are using Cumulus version 1.8.8 build 875 or higher you may also use the strings.ini file included in this zip and place it within your Cumulus application folder. This file includes translations for all the forecasts, moon phases, beaufort and pressure trends.
*The next time Cumulus performs a web update your site will be in Portuguese
Warning: If you upgrade your version of Cumulus these files will be replaced with the standard files so you will need to repeat the above process. If you make any customisation to these please take a backup before upgrading otherwise you will have lost your work.
=Version Control=
*1.0 First release
Category:Other Languages
Privacy policy

==Cookies==
The sites set a temporary session cookie on a visitor's computer whenever a page is visited. Readers who do not intend to log in or edit may deny this cookie; it will be deleted at the end of the browser's session. More cookies may be set when one logs in to maintain logged-in status. If one saves a user name or password in one's browser, that information will be saved for up to 30 days, and this information will be resent to the server on every visit to the same Project. Contributors using a public machine who do not wish to show their username to future users of the machine should clear these cookies after use.
==Page history==
Edits or other contributions to a Page or its articles, user pages and talk pages are generally retained forever. Removing text from a project does not permanently delete it. Normally, anyone can look at a previous version of an article and see what was there. Even if an article is "deleted", a user entrusted with higher level of access may still see what was removed from public view. 
==User contribution==
User contributions are also aggregated and publicly available. User contributions are aggregated according to their registration and login status. Data on user contributions, such as the times at which users edited and the number of edits they have made, are publicly available via user contributions lists, and in aggregated forms published by other users.
==Personal Information==
We retain no details beyond your email address, username, password and full name if provided by you. No other information is requested, required, or stored. It is your responsibility to refrain from posting personal information about you or another person -- this is in clear breach of our terms of service