nyuuzyou/wikis huggingface dataset:
WeatherConsole

The WeatherConsole is an simple web page presenting 'live' and automatically updating information to viewers. It is a text based display, and is easily customised to suit your own site design.
Click on the example screen shot on the right. Alternatively see the console live at http://azer.com.au/weather/WeatherConsole/
=Requirements=
*a website
*Cumulus realtime.txt file being updated regularly by Cumulus
Category:User Contributions
=The Basics=
*download the following file...CumulusWeatherConsole.zip 
*Unzip the contents (five files will be extracted)
*Edit the file wconsole.js. There are two lines which need modified at the top. The location of your realtime.txt data file, and how often to refresh the display.
*Copy all the files to your web site into a subfolder, or the root -- your choice
*open wconsole.html in a browser
=Usage=
By default the Console is displayed within a current browser, however clicking on the icon on the bottom right of the screen will pop-out the Console to it's own window and can be left running in the background.
=Possible problems=
*If the WeatherConsole can not find your realtime.txt file it will give an error. Check the setting in wconsole.js. The location is typically a folder location on your webserver. Examples could be /realtime.txt or /data/realtime.txt
=Personalising=
*Edit wconsole.html and modify the wording after <TITLE> on the 6th line. This is the text to be displayed in the title bar at the top of the window. You may also wish to edit line 20 to a more personalised title shown within the browser itself.
*All colouring can be adjusted in the stylesheet file wconsole.css
=Version Control=
1.2 Fixed problem with Beaufort descriptions; two were missing!
1.1 Added 'pop-out' feature 
1.0 Public launch
Category:WebTools
WeatherLink Live

== Davis WeatherLink Live ==
The Davis WeatherLink Live device is fully supported by Cumulus MX.
Cumulus MX also supports historic data catch-up by using the Davis WeatherLink.com cloud data source - though this does require you to have a Pro licence to enable the feature.
There are a few caveats around this though...
* You must have at least a Pro subscription for your device on weatherlink.com to grant access to the historic data.
* The new APIv2 used to access the data.
* The APIv2 keys are now available via weatherlink.com.
If you meet the criteria, then these are the steps you need to follow...
# Sign on to the Davis weatherlink.com web site with your normal username/password
# On weatherlink.com open your user profile, you will see a section titled API Key v2
# If you do not already have a key and secret displayed, click "Generate v2 key" to create them. Copy these strings somewhere safe so you can later paste them into Cumulus
# Ensure you are running Cumulus MX v3.4.0 or later
# If this your first run of CumulusMX.
## Add a local firewall rule on your server to enable UDP port 22222 inbound
## Go into the Station setup and select Davis WLL as the station type
## In the WLL section enter your API key and secret. LEAVE THE STATION ID BLANK
## Set up your sensor to transmitter ID mappings if different from the defaults
## It is not necessary to enter the WLL IP address if you only have one device, Cumulus should just find it on your network. But if you know it, it does not harm to enter it, Cumulus will change it anyway if your WLL ever changes address.
## Save the setup
## Restart Cumulus
# If you only have a single station registered with weatherlink.com, then Cumulus should discover its ID automatically and start using it
# But if you have more than one, the Cumulus will list their API IDs and names in the console window.
# Note the ID you want to use. Go back into the Station setup and enter the ID there. You do not need to restart Cumulus after that.
# Enjoy! Cumulus should now download missing data for periods it is stopped.
There is effectively no limit on how much historic data you can download++, I have tested using a four day catch-up without issues.
Davis impose rate and data limits on the APIv usage- currently they are...
* 300 API calls per hour, or 2 API calls per second
* 24 hours of data in any one call
Cumulus honours these restrictions.
The APIv2 uses both a key and a secret that encrypts part of the URL making playback or emulating the API calls by another user impossible. A nice feature other web APIs could emulate.
++Cumulus MX will get the max 24 hours data per call if required, which will give a limit of 300 days of historic data catch-up.
Web folder

For MX (from 3.10.1 onwards), the /web folder (when you unzip the distribution) contains some template files which you can optionally tailor (although any tailored file will get overwritten when you upgrade). However, the main purpose of the folder is to hold files created by the Cumulus code when you are running the software, ready for updating to your web site. These files contain data and have the file extension .json. Obviously, files created by the code cannot be tailored, but (depending on release) you may be able in Settings control whether these files are generated and whether they are uploaded.
Note that MX (from 3.10.1 onwards), uses web pages that are uploaded only once onto your web server. The data needed to populate most of these web pages is supplied by websitedata.json file in /web folder, which Cumulus will process and upload at regular interval. 
In older releases of MX, the /web folder (when you unzip the distribution) contains many template files, these files contain a web page structure and represent data by web tags that MX will process. Some of these have filenames of pattern xxxxxT.htm. When you are running the Cumulus MX software, additional files are created in the /web folder, some of these will have .htm file extension, others will have .json file extension. Again some files can be tailored (although any tailored file will get overwritten when you upgrade), and some will be generated from internal code and cannot be tailored. 
When you install the legacy Cumulus (up to version 1.9.4), a set of template files is included. As Steve Loft said, "They exist because these are our (Beth and Steve Loft) web pages, we never imagined people would use them without modification". Cumulus can process these templates (on a regular interval) and create web pages which it them uploads to your web server.
If you decide to use your own template files, perhaps as described here with PHP script, it is best if you store them in a different folder. More information on the Customised_templates page.
Category:Cumulus FilesCategory:Cumulus 1Category:Cumulus MX
Webfiles folder

Category:Cumulus 1Category:Cumulus FilesCategory:Cumulus MX
The webfiles (all lowercase) folder in both the legacy Cumulus and MX contains sub-folders and files that need to be uploaded to your web server in a on-off operation, if (and only if) you want to use the standard web pages provided as examples with Cumulus.
If your web server is provided by an organisation, then you will need to use a FTP, SFTP, or FTPS
If your web server is only going to be used for web pages related to Cumulus, 
#upload the contents of the /webfiles' folder to your root folder (do not create a "webfiles" sub-folder) on your web server. 
#Preserve the structure for any sub-folders, so files on your web server are in same position relative to root that they were relative to webfiles.
If your web server is to be used for other purposes, you might want to create a sub-folder (perhaps called weather) under your root folder for the contents of webfiles.
The contents of this folder may vary between releases.
For Cumulus 1, please see Simple_Website_setup#Folders_and_Files_to_Transfer_just_Once. There are lots of files, some in sub-folders.
For MX releases 3.0.0 to 3.9.7, the instructions that existed in this Wiki (with list of sub-folders and files) have been removed. But like the legacy Cumulus and later MX releases, you simply copy the entire folder to your web server, preserving structure as described above.
For any release of MX from 3.10.1 onwards, please see 3.10.1 web site installation, although it says no more than has been said above.
Website setup

Cumulus allows you to create web pages which can either be viewed only on your computer or made available to all via the internet. 
To put them on the internet, 
* you must have web space on the internet which allows standard FTP access. 
* you will require an FTP tool (not essential if you are using your own computer to both run cumulus and to act as web server as in that case you can copy files between locations at setup and turn off FTP on Cumulus). 
== webspace ==
Webspace is available commercially (paid) or free from a variety of sources. Your internet service provider (ISP) may provide you with some space.
It is worth checking that any free provider allow FTP -- example, Google does not allow FTP as part of it’s Sites package so you can not use this with Cumulus. If you are not sure, ask your webspace provider or check the email they sent you when setting up your webspace. They will mention the FTP server in the email or support website.
Many of the ‘free’ offerings will also want to automatically insert adverts on your page, and may have other restrictions.
== FTP tool ==
This is a tool which transfers files from your computer onto your webspace. As a minimum you will need this tool to transfer some files as a one-off at setup. There are a huge array of FTP tools, both commercial and free.
If you can get your FTP tool to work, then the host, username, password and (optional) directory it uses to transfer the initial files are exactly the ones you will need to enter into the Cumulus Internet Configuration screen. See cumulus help for more information. It is worth noting that although the FTP host is usually expressed as a FTP address (e.g. 'ftp://' might be the initial part of an internet based address), it can be expressed as a numerical location (e.g. 127.0.0.1 might be the location of a web server based on your computer, xxx.yyy.u.vvv is a mask denoting a general internet based address) both in your FTP tool and in cumulus.
== Implementation Alternatives ==
*Simple Website setup -- this is the easiest way using the pages, scripts, and images provided in the cumulus package, it requires minimal setup from you and gets your data online in minutes. It is ideal for those who are not familiar with writing web pages.
*Customised templates -- one step on from the above method, this article tells you how to adapt the default pages Cumulus will produce with some minor changes.
*Use designs from other providers such as this one designed specifically for Cumulus 1 or MX. There are others like this suite in JavaScript (AJAX) and PHP Hypertext preprocessor languages that work with various weather software. Some people have designed implementations that are intended to present Cumulus data in a more sophisticated manner, these may require additional tools (e.g. the server based language PHP) to be provided with your webspace in order to create web pages from a number of sources
*Write your own -- for more advanced users who understand HTML (the language of web pages on the internet), and the supporting styles and scripts, this allows you to group data from Cumulus in any way you like.
 Category:WebTips
Wind chill

Wind chill is the apparent temperature felt on exposed skin due to wind. 
*The degree of this phenomenon depends on both air temperature and wind speed. The greatest wind chill reported in extremes, results from a combination of a low temperature and a high wind speed. 
*The wind chill temperature (often popularly called the wind chill factor) is always lower than the air temperature. In cases where the apparent temperature is higher than the air temperature, the heat index is used instead.
Some weather stations provide a Wind Chill reading and, by default, that reading will be used by Cumulus.
#If within Cumulus you apply corrections (Configuration menu, Calibration screen) to either temperature or wind speed, then any wind chill output by your station will not be compatible, and you should set Cumulus to Calculate Wind Chill.
#On Configuration menu click Station and tick the option to Calculate Wind Chill.
*There may be other reasons why you do not want to use the reading provided by your station and tick this option.
*If your weather station does not provide a Wind Chill reading, Cumulus will calculate it (regardless of whether the option is ticked or not). 
Wind Chill Temperature is officially defined for temperatures at or below 10 °C (50 °F) and wind speeds above 4.8 kilometres per hour (3.0 mph).
*For lower wind speeds, Cumulus will report a wind chill temperature that will be the same as reported for temperature. 
*By default, for higher temperatures, Cumulus will report a wind chill temperature that will be the same as reported for temperature. Cumulus can make a wind chill calculation for temperatures above 10°C, so if you have asked Cumulus to calculate wind chill and don't wish it to comply with the ten degree limit, edit your cumulus.ini and add to the [Station] section the line: UseWindChillCutoff=0
More information on Wind Chill here in Wikipedia. Cumulus uses the 'new North American' formula, as described on that page. For a discussion on the usefullness of wind chill in Canada see here.
Category:Terminology
Windrun

A measurement of how much wind has passed a given point in a period of time. A wind blowing at three miles per hour for an entire hour would give a wind run of three miles.
Cumulus calculates wind run by noting the average wind speed every minute (assuming the software remains running). Wind run is calculated by adding in a minute's worth of 'distance' corresponding to that speed. So the wind run for a particular period is effectively an indication of the average wind speed over that period. There are 1,440 minutes in a day. A wind speed measured in distance units divided by minutes, would give a wind run numerically equal to the speed each minute. A wind speed measured in distance units divided by hours, would give a wind run numerically equal to the speed when calculated for a period of an hour. 
A wind run of 240 miles over the course of a day, for example, means that the average (of typically 1,440 measurements of) wind speed over the 24 hour day was 10 mph. Cumulus stores the wind run for each day in dayfile.txt.
Category:Terminology
Wxnow.txt

The wxnow.txt file is created by Cumulus once a minute by default, in the Cumulus program folder, unless you have disabled it by setting
CreateWxnowTxt=0
in the [Station] section of Cumulus.ini_(Cumulus_1). Below is the file format, simply for information. 
=Sample File=
This is a simply text file containing two lines of data.
 Feb 01 2009 12:34
 272/010g006t069r010p030P020h61b10150
=Format of the file=
The first line is the time the file was created in local PC time. Please note that the day of the month, the hour and the minute must be padded to two digits with zeros if needed.
The second line is the wx report, in the format used in APRS "complete weather reports". The format is:
*272 - wind direction - 272 degrees
*010 - wind speed - 10 mph
*g006 - wind gust - 6 mph
*t069 - temperature - 69 degrees F
*r010 - rain in last hour in hundredths of an inch - 0.1 inches
*p030 - rain in last 24 hours in hundredths of an inch - 0.3 inches (Cumulus does not supply this value)
*P020 - rain since midnight in hundredths of an inch - 0.2 inches
*h61 - humidity 61% (00 = 100%)
*b10150 - barometric pressure in tenths of a millibar - 1015.0 millibars
Category:Configuration Files
From build 1028 of version 1.9.2:
* Fix negative (F) temperatures
From Build 1097 of version 1.9.4: 
* Selecting APRS/CWOP option to send solar radiation now also adds it to wxnow.txt
* Pressure in wxnow.txt is now 'altimeter' rather than MSLP
Xml webtags

Cumulus automatically prepares a number of webpages by using HTML template files. These files contain webtags which Cumulus replaces with actual values from your weather station.
XML Webtags takes this a step further and produces a full list of webtags in an XML format. You can then include this file when building your own webpages or weather tools.
The XML file contains all current webtags produced by Cumulus.
A similar project is available for PHP Webtags
=Installation=
*Download https://cumuluswiki.org/files/xmltemplate.1.8.zip
*Unzip the files, which will produce one file (cumulusxml.tpl)
*Copy the file into your Cumulus folder on your PC
*Within Cumulus click Configuration, Internet, then the 'Files' tab
*Add a new entry in one of the blank lines. 
::Local filename is the full path and filename of cumulusxml.tlp
::Remote filename can be anything however it should be the path to your HTML files and a filename, ending in XML. 
*You must tick 'Process' and 'FTP' to allow Cumulus to add values to the file and upload it.
*Optionally, if you wish to produce an XML file in realtime tick the 'Realtime' option too. Only use this option if the tool you are using with XML on your website expects almost live data. WARNING -- this will generate a significant amount of data upload throughout the day as each XML upload is about 56k. If you do this in realtime (say every 15 seconds) that is 320Mb per day. If you have bandwidth limitations this could be a problem
Category:User Contributions
=Example Output file=
relatime.xml -- Note this file has been truncated simply to show the start and end of the file.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--Cumulus WebTag XML Data file - version 1.6-->
<weatherdata>
<timetags>
 <item name="date">
 <value>05/09/2009</value>
 <unit></unit>
		<image></image>
		<class>dynamic</class>
		<description>The current date</description>
	</item>
	<item name="time">
		<value>17:40 on 05 September 2009</value>
		<unit></unit>
		<image></image>
		<class>dynamic</class>
		<description>The current time</description>
	</item>
	<item name="day">
		<value>05</value>
		<unit></unit>
		<image></image>
		<class>dynamic</class>
		<description>The current day as a 2-digit number</description>
	</item>
	<item name="dayname">
		<value>Saturday</value>
		<unit></unit>
		<image></image>
		<class>dynamic</class>
		<description>The current day as a word</description>
	</item>
	<item name="shortdayname">
		<value>Sat</value>
		<unit></unit>
		<image></image>
		<class>dynamic</class>
		<description>The current day as a shortened word</description>
:
:
:
	<item name="RCwgustTM">
		<value>10.7</value>
		<unit><![CDATA[ mph]]></unit>
		<image></image>
		<class>dynamic</class>
		<description>Recent high wind gust</description>
	</item>
	<item name="RCwspeed">
		<value>4.2</value>
		<unit><![CDATA[ mph]]></unit>
		<image></image>
		<class>dynamic</class>
		<description>Recent wind speed</description>
	</item>
</nocommatags>
</weatherdata>
Category:WebTools
Yadr

== Introduction ==
This module provides access to the daily data as found in the dayfile.txt datafile. Only a limit number of weather variables is displayed as not all data are deemed important (like derivatives, EVT or wind direction). This is not the first Dayfile Reader and probably not the last therefore its name: YADR (Yet Another Dayfile Reader).
Other dayfile readers, notably the beteljuice one, use PHP, MySql and daily transfer of the Dayfile to the website which require a totally different technical and data infrastructure. If you wish you can simply use that one beside CumulusUtils. The tools don't bite each other.
The work of both beteljuice and Murry Conarroe of Wildwood Weather helped a lot in determining the how and what.
== Operation ==
This module is included in the website. When needed as a single output the following command is given:
 utils/bin/cumulusutils.exe Yadr
== Output ==
The output of the YADR module consists of the following files:
#Yadr.txt which contains the javascript menu, the css and the HTML container code.
#YadrTempYYYY.txt which contains the colour formatted data table for the temperature for year YYYY.
#YadrRainYYYY.txt which contains the colour formatted data table for the rain for year YYYY.
#YadrWindYYYY.txt which contains the colour formatted data table for the wind speed for year YYYY.
#YadrWindRunYYYY.txt which contains the colour formatted data table for the wind run for year YYYY.
#YadrPressYYYY.txt which contains the colour formatted data table for the pressure for year YYYY.
#YadrHumYYYY.txt which contains the colour formatted data table for the humidity for year YYYY.
See Thrifty for efficiency considerations.
== Inifile parameters ==
The YADR module has no inifile parameters of its own. However, it borrows the parameter WindrunClassWidth from the Graphs section in order to create the legend for the Windrun table. As a result - and in the rare occasion of - IF you only use YADR, you will notice the WindrunClassWidth parameter in the graphs section even though you do not use graphs.
For the use of WindrunClassWidth for this report, see the page on Wind Charts.
== Inner working ==
In a simple loop of the years, the tables are created in three steps:
#Within simple loops over days and months the formatted table of values is created
#Within a simple loop over the months the statistics are calculated using the LINQ functions Count, Sum, Min, Max and Average.
#Finally the legend is written assuming a fixed number of thirteen classes dividing the space between the assumed extremes. The extremes can be limits (never a negative amount of rain) or open values (there is no upper or lower limit for temperature) for which the legend is adapted.
Category:CumulusUtils
Main Page

Attentionlab Wiki
Welcome to the main page of the Attentionlab Wiki.
Here you can find the information and documents needed to help you with doing research within our group.
If anything is missing or incorrect; contact us and we will add, adjust or just about remove anything at your whim. Sort of.
Be sure to check out our House Rules before doing any experimenting!
----
Updates:
- 2nd of February, 2016: Added a document by Jessica Heeman on Holm-Bonferroni corrections. AttentionLab approved!
- 21st of May, 2015: You can no longer use the paper forms to apply for participant money. The system has been replaced by a digital form system. The digital forms can be found under Documents (down below).
----
Sources:
Documents
House Rules
----
Links:
Link to main site
Twitter account
Documents

Documents and links to relevant documents. Yay, documents are your friends!
----
Resources:
Eyelink 1000 manual; i.e. your best friend when you run into problems.
Quick guide to configure the eyelink for your experiment. It's a bit more readable than the full manual for a quick setup.
A concise summary on the Holm–Bonferroni method, courtesy of Jessica Heeman.
----
Forms(in Dutch):
A list to let your participants sign that they have received their money (or whatever they may be receiving) for participation.
If you would like to apply for money for your research you can use this link: Proefgeld
----
Manual, Informed Consent and Signature list:
Please refer to this manual before testing in the labs; the last two pages are an example informed consent and a signature list.
Link to file; redirects to dropbox