Basic Usage: Difference between revisions

From Mulka2
Jump to navigation Jump to search
No edit summary
 
(25 intermediate revisions by the same user not shown)
Line 2: Line 2:
== Flow of operation ==
== Flow of operation ==
* Before the race
* Before the race
** Make an event data
** Create an event data
** Input participants data
** Input participants data
** Input courses data  
** Input courses data  
* The race day
* On the race day
** Input direct entries  
** Input direct entries  
** Download runners’ card data
** Download runners’ card data
Line 12: Line 12:
** Publish results to website
** Publish results to website


== Make an event data ==
== Start Menu ==
Launch 'Event Manager' and make an event data.
[[File:start-menu.png|upright=1.5|thumb|none]]
[[File:make-event-1.png|frame|center|Click 'New Event' button]]
;Network Manager
<br/>
:[[Network Manager]] is used when Mulka2 is used by multiple computers via a network.
:It is also used for connecting cloud server to use cloud service (web application).
;Main Window
:[[Main Window]] is used for non-score event's regular operation on the event day.
;Other
:This function is used for starting [[Score-O Viewer]] (a tool for Score-O data processing) and [[Large Screen]] (a tool for outputting the data to a big TV screen) and so on.
;Event Manager
:[[Event Manager]] is used for creating event data (original setting for each event).
;Configuration
:[[Configuration]] is used when you want to change font name, size and location of data folders.


Input basic information of the event.
== Before the race ==
[[File:make-event-2.png|frame|center|Input basic information]]
In standard event, make a new event data by using '[[Event Manager]]'.  
* Fill 'Event Name' and 'Date' fields.
* 'Filename' field is automatically filled when 'Date' is filled. Please change more handy name.
* Other fields are optional.


[[File:make-event-3.png|frame|center|Click 'OK' button.]]
For standard foot-o competition, it is necessary to input entry list and class and course data.
<br/>
For training event, you can omit entry list by using ’[[Direct Entry]]' feature or '[[Orienteer Name Database]]' feature.
For score-o event, it is necessary to input score for each controls instead of course data.


== Input data before the race ==
* [[Create a New Event Data]]
Data which are required to input
* [[Input Start List|Input Entry List]]
* Class
* [[Course Setting]]
* Course
* [[Class Setting]]
* Score of each control (Score-O)
* [[Score-O Setting]]
* Startlist
* [[Relay Setting]]
* Other files which depend on event style
* [[Data File Specification]]


== On the race day ==
Software which is mainly used is different by event style.
'Main Window' is used for non-score race and 'Score-O Viewer' is used for score race.
[[File:basic-usage-1.png|upright=1.5|thumb|none|Launch Main Window or Score-O Viewer]]
* [[Main Window|Basic operation of Main Window]] (Basic operation of Score-O Viewer is similar)
* [[Direct Entry]]
* [[Download finished runner’s card data]]
* [[Print Result List]]


There are two ways for input.
== Saving data ==
# Use files
All data with 'Main Window' and 'Score-O Viewer' are automatically saved in real-time. Do not worry about missing the data.
# Input on screen
* The processed data are saved in a file named 'changes.dat' in the data folder.
* The 'changes.dat' file records all change tracking as text format. It may be possible to edit the raw data directly.


To input data, launch 'Event Manager' and select the event.
<br/>
If you use files, make 'Startlist.csv' and import it at first.
----
If you input startlists on screen, click ‘Add’ to define classes at first.
[[Mulka2|[Back to Top Page]]]
[[File:input-data-1.png|frame|center|There are two ways to input data.]]
 
[[File:standard-startlist.png|thumb|500px|center|Standard startist.csv]]
Pleese see '[[Startlist.dat]]' for complete field list of startlist.csv.
<br />
 
To input participants information on screen,
select ‘Entry list’ tab and click [Add].
[[File:input-data-2.png|frame|center|Input participants information ]]
 
Input start number, class, start time, card number, competitor name1 and club name1.
Start number is mandatory to identify the data, but any unique number is available.
It is changeable later by editing ‘startlist.dat’ in data folder directory by using MS Excel or other software.

Latest revision as of 14:53, 23 April 2017

Flow of operation

  • Before the race
    • Create an event data
    • Input participants data
    • Input courses data
  • On the race day
    • Input direct entries
    • Download runners’ card data
    • Print results
  • After the race
    • Publish results to website

Start Menu

start-menu.png
Network Manager
Network Manager is used when Mulka2 is used by multiple computers via a network.
It is also used for connecting cloud server to use cloud service (web application).
Main Window
Main Window is used for non-score event's regular operation on the event day.
Other
This function is used for starting Score-O Viewer (a tool for Score-O data processing) and Large Screen (a tool for outputting the data to a big TV screen) and so on.
Event Manager
Event Manager is used for creating event data (original setting for each event).
Configuration
Configuration is used when you want to change font name, size and location of data folders.

Before the race

In standard event, make a new event data by using 'Event Manager'.

For standard foot-o competition, it is necessary to input entry list and class and course data. For training event, you can omit entry list by using ’Direct Entry' feature or 'Orienteer Name Database' feature. For score-o event, it is necessary to input score for each controls instead of course data.

On the race day

Software which is mainly used is different by event style. 'Main Window' is used for non-score race and 'Score-O Viewer' is used for score race.

Launch Main Window or Score-O Viewer

Saving data

All data with 'Main Window' and 'Score-O Viewer' are automatically saved in real-time. Do not worry about missing the data.

  • The processed data are saved in a file named 'changes.dat' in the data folder.
  • The 'changes.dat' file records all change tracking as text format. It may be possible to edit the raw data directly.



[Back to Top Page]