How to use Redmine for the GEOFON Network¶

The following guidelines are for both GEOFON internal and partners co-operating the GE stations.
Redmine is used as a documentation tool and ticket system for GEOFON.
Inside a project you have different tabs. The most important ones are:

Issues: An overview of all former and current problems. Here it is also possible to edit already existing issues.
New issue: There seems to be a still not reported problem with the station? Here new issues can be committed.
Wiki: Documentation of the station. Which hardware is installed? How to access it remotely? ...

Issues¶

Issues are used to document actions and problems concerning the stations, thus it can also be used as history of a station.

Editing an issue:

Right click the issue to modify and select 'Edit' or click on the issue number and click 'Edit' afterwards
All new commands/actions should be written in the 'Notes' field. A detailed and comprehensible description is welcome.
Changing the status: A project should be closed just after a second check. If the problem was just solved, set the status to 'Resolved'.
If necessary, the subject and description can be edited. See the following section for how this fields should be filled.
Use UTC for times. A good place to note the timestamp is the comment line of 'Log Time', but anywhere, for times should be used UTC.

New issue¶

To document an action or to report a new problem, click on the tab 'New issue'. It is necessary to fill at least a subject.

Agreements about the sections (followed by examples of issues):

Tracker: When a problem occurs it may not be clear what kind of action will be involved in the solution. In such a case use the tracker 'Problem'. In general we use the tracker to separate between actions we (GEOFON team) perform directly on site (Tracker = Onsite maintenance) from actions carried out from remote by us (GEOFON team) with or without the local partner's support (Tracker = Remote maintenance/support).
Subject: Topic. Furthermore Tags are used to specify the type of action. At the bottom of this page there is a short list of possible tags.
Description: Short(!) summery about the problem and how it was resolved. For a detailed description of the problem and the solution, use the 'Notes' category. Which is accessible just after the creation of a new issue. Afterwards go to the tab 'Issues' and edit the issue, which was just created.
Assignee: If it's not clear whose responsibility it is, let it free.

Examples¶

If you can't solve the problem yourself, just report it. If you feel uncomfortable with this tool (Redmine), just write an email to geofon_maint@gfz-potsdam.de.

Sensor out of range, onsite or remote mass centering needed¶

Tracker: Remote maintenance/support
Subject: #Masscenter E component out of range
Description: East component was out of range, remote mass centering done on date and UTC time
Assignee: <me>

SeiscompBox was hanging¶

Tracker: Remote maintenance/support
Subject: #Powercycle SeiscompBox was hanging
Description: No data transmission due to hanging SeiscompBox solved with power cycle.
Assignee: <me>

Note (01.02.2020):
No data since 30.02.2020. Seiscomp not reachable. After a power cycle via the T-Elektronik we receive data again.

Installation of new mobile router¶

Tracker: Onsite maintenance
Subject: #Shipment #New mobile router
Description: Problem with internet connection, installation of additional mobile router as backup
Assignee:

Note (03.03.2020):
Since 02.03.2020 we don't receive data anymore. No possibility to reach the station from GFZ. <person1> informed.

Note (04.03.2020):
Reply mail: "There is a problem with the local lan, which needs some time to be resolved. Power is fine." 
We will send a preconfigured mobile router (Teltonika RUT955) and they will provide the SIM.
Information about Teltonika: ... with VPN xxx.xx.xx.xx

Note (07.03.2020):
Package arrived, router was installed with local SIM (phone number:+xxxxxxxxx). The data center is informed to change the IP to the new mobile router

Note (07.03.2020): 
We receive data again.

Note (15.04.2020):
Problem of local lan solved. Data now comming again via xxx. Teltonika will be kept as a backup.

No data (still existing problem)¶

Tracker: Problem
Subject: #Nodata
Description: 
Assignee:

Note (01.02.2020):
No data since 01.02.2020. We checked the following: We can reach the VSAT modem, but not the seiscomp. Wago is also not responding. Network problem?
We have to visit the station for further investigations.

Note! In case of no data since "date" please make sure the start date of the ticket/issue is the day of the last data received at GEOFON DC

We got informed that the Broad-band sensor may have a wrong orientation¶

Tracker: Metadata
Subject: #Feedback #SensBB wrong orientation
Description: Wrong orientation of sensor, Metadata change for that period
Assignee: <person2>

Note (01.02.2020):
We got an email from <person3> that the information in the metadata regarding the sensor's orientation doesn't fit to the real orientation between 2014 and 2015.
Send a mail to <person4> to check this and asked <person5> if he can remember if something had changed during that time.

Note (01.02.2020):
<person5>: During that time the sensor had another place. Thus it would be possible that during the new installation happened a mistake.

Note (03.02.2020):
<person4>: We found a miss-orientation for that period of xx.xx degree. That would fit if we miss-interpreted the sign of the magnetic declination.

Note (03.02.2020):
Change of metadata between 2014 and 2015.

The installed hardware, access information, contact information of local partners,... can be found under the tab 'Wiki'.
Please write to geofon_maint@gfz-potsdam.de if you find some errors in this documentation (or edit it by yourself).

[Please note that the access information, e.g. IPs may just be reachable from the GFZ network]

Files (0)

Updated by Thomas Zieke 3 months ago · 19 revisions

Project

General

Profile

Redmine

Wiki