tseries:technical

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
tseries:technical [2014-01-22 06:59:44]
juergens 		tseries:technical [2022-05-31 09:29:32] (current)
Line 1: Line 1:
 ====== Tseries Technical Documentation ====== ====== Tseries Technical Documentation ======
- 
  
  
 ===== Description: ===== ===== Description: =====
  
-Tseries is an open-source time-series viewer for meteorological purposes. Tseries is developed and implemented at the Norwegian Meteorological Institute met.no, as a part of the operational meteorological workstation. Tseries can be used standalone, or in  interaction with the DIANA meteorological workstation. +//Tseries// is an open-source time-series viewer for meteorological purposes. //Tseries// is developed and implemented at the Norwegian Meteorological Institute met.no, as a part of the operational meteorological workstation. //Tseries// can be used standalone, or in  interaction with the [[https://diana.wiki.met.no/doku.php|Diana]] meteorological workstation. 
-The tseries package contains two programs:+The //Tseries// package contains two programs:
  
   - tseries.bin is the timeseries viewer with a Graphical user interface   - tseries.bin is the timeseries viewer with a Graphical user interface
-  - btseries is a batch version of tseries, using the same graphical engine+  - btseries is a batch version of //Tseries//, using the same graphical engine
  
  
-The Goal of this Document is to explain the basic structure of tseries setup- and stylefiles in order to adapt tseries to a specific environment. The intended readership for this document is it-personnel and meteorologists, in charge of the operational setup of a local tseries implementation. The description of the tseries GUI is integrated in the applications help menu. The btseries user interface is described in the “btseries –help” option. +The Goal of this Document is to explain the basic structure of //Tseries// setup- and stylefiles in order to adapt //Tseries// to a specific environment. The intended readership for this document is it-personnel and meteorologists, in charge of the operational setup of a local //Tseries// implementation. The description of the //Tseries// GUI is integrated in the applications help menu. The btseries user interface is described in the “btseries –help” option.
  
  
 +Styles and control are located in a separate package - The source code is downloadable at [[https://svn.met.no/tseries/config|subversion]]
 ===== Command line parameters: ===== ===== Command line parameters: =====
  
-Most of the input in tseries is given by the control file, but can be overridden by command line input: +Most of the input in //Tseries// is given by the control file, but can be overridden by command line input: 
- +|     |  
-| **-s [ setupfile ]** | if the setup file is not directly defined or invalid, tseries will try to find a valid setup file with the name tseries.ctl in the system. First looking in the current directory, then in $HOME/.tseries/ and at last in /etc/tseries. If no valid setupfile exists, tseries will exit. |+| **-s [ setupfile ]** | if the setup file is not directly defined or invalid, //Tseries// will try to find a valid setup file with the name tseries.ctl in the system. First looking in the current directory, then in $HOME/.tseries/ and at last in /etc/tseries. If no valid setupfile exists, //Tseries// will exit. |
 | **-S [site]** | site is just a short string. The user can define elements in the setup-file that  are only used by certain groups. By this, several groups of users can share one setup-file to simplify maintenance.    | | **-S [site]** | site is just a short string. The user can define elements in the setup-file that  are only used by certain groups. By this, several groups of users can share one setup-file to simplify maintenance.    |
 | **-l [lang]** | The language for the GUI. Can be configured in the GUI itself. Available languages are English(default), Norwegian Nynorsk, Norwegian Bokmål, Swedish, German, French. New languages can be added by using the qt-linguist tool. |      | **-l [lang]** | The language for the GUI. Can be configured in the GUI itself. Available languages are English(default), Norwegian Nynorsk, Norwegian Bokmål, Swedish, German, French. New languages can be added by using the qt-linguist tool. |     
-| **-T [title]** | Changes the window title, useful if you are running several instances of tseries at the same time.     | +| **-T [title]** | Changes the window title, useful if you are running several instances of //Tseries// at the same time.     | 
-| **-H [wdbhost]** | Host for the WDB connection |    +| **-H [wdbhost]** | Host for the [[https://wdb.wiki.met.no/doku.php|WDB]] connection |    
-| **-u [wdbuser]** | User for the WDB connection |   +| **-u [wdbuser]** | User for the [[https://wdb.wiki.met.no/doku.php|WDB]] connection |   
 | **-d [section1:key1=token1 section2:key2=token2] ** |  The user can override any entity in the setup file by this option. Example: Use a different Diagrams definition file, without changing the setup file, by the option -d files:Defs=./tsDiagrams.def | | **-d [section1:key1=token1 section2:key2=token2] ** |  The user can override any entity in the setup file by this option. Example: Use a different Diagrams definition file, without changing the setup file, by the option -d files:Defs=./tsDiagrams.def |
  
Line 34: Line 33:
 ===== Datastreams: ===== ===== Datastreams: =====
  
-There are several possibilities to add a Datastream to a tseries Diagram:+There are several possibilities to add a Datastream to a //Tseries// Diagram:
  
   - **HDF** is the most common used datasource. In HDF all positions are predefined and named, Hdf input is defined in the base control file tseries.ctl. All HDF streams mentioned in tseries.ctl are indexed at startup. Streams from different HDF files can be combined in a single Diagram.   - **HDF** is the most common used datasource. In HDF all positions are predefined and named, Hdf input is defined in the base control file tseries.ctl. All HDF streams mentioned in tseries.ctl are indexed at startup. Streams from different HDF files can be combined in a single Diagram.
   - **ASCII** is implemented. But in an operational environment ASCII streams are space-consuming and ineffective. An example of usage of ASCII streams is presented in the appendix of this Document.   - **ASCII** is implemented. But in an operational environment ASCII streams are space-consuming and ineffective. An example of usage of ASCII streams is presented in the appendix of this Document.
-  - **WDB** the Weather and Water Database WDB is an  open-source database system based on postgres. The system is developed at MET Norway. WDB is holding data as fields. Tseries retrieves interpolated timeseries  from the database.  As WDB interpolates data on-demand, WDB is more flexible, but slower than local HDF files. WDB is the dataengine for for the web-based, free weather service yr.no +  - **WDB** the Weather and Water Database [[https://wdb.wiki.met.no/doku.php|WDB]] is an  open-source database system based on postgres. The system is developed at MET Norway. [[https://wdb.wiki.met.no/doku.php|WDB]] is holding data as fields. //Tseries// retrieves interpolated timeseries  from the database.  As [[https://wdb.wiki.met.no/doku.php|WDB]] interpolates data on-demand, [[https://wdb.wiki.met.no/doku.php|WDB]] is more flexible, but slower than local HDF files. [[https://wdb.wiki.met.no/doku.php|WDB]] is the dataengine for for the web-based, free weather service yr.no 
   - **KDVH** is a MET Norway proprietary interface, based on URL. KDVH reads observations from the Norwegian climatic database. The Data are defined as Diagram entries in the control file (tseries.ctl) and can be implemented in any diagram.    - **KDVH** is a MET Norway proprietary interface, based on URL. KDVH reads observations from the Norwegian climatic database. The Data are defined as Diagram entries in the control file (tseries.ctl) and can be implemented in any diagram. 
 +
 +  - **Fimex**  [[fimex:start|Fimex]]  is a library to process several datastream types (like NetCDF).  [[fimex:start|Fimex]]  Interpolates on demand from files. This is time-consuming, therefore fimexstreams are read for all positions on request. After that the  [[fimex:start|Fimex]]  stream is used from cache
  
 ===== Diagrams: ===== ===== Diagrams: =====
  
-A Diagram in tseries consist of one or more datastreams connected to a given style. There are several files needed to generate a diagram:+A Diagram in //Tseries// consist of one or more datastreams connected to a given style. There are several files needed to generate a diagram:
 To generate a new diagram, one have to proceed the following workflow: To generate a new diagram, one have to proceed the following workflow:
  
Line 67: Line 68:
  Tseries.ctl is a multi-user setup-file. To avoid the administration of several setup-files within one company, the file can contain several different configurations. The file is processed top-down. If a variable is defined several times, the last definition is valid.  Tseries.ctl is a multi-user setup-file. To avoid the administration of several setup-files within one company, the file can contain several different configurations. The file is processed top-down. If a variable is defined several times, the last definition is valid.
  
-Elements within sites in tseries are usually inactive, the parser will ignore them, unless the user starts tseries with the flag that defines the specific site ( the -S flag). A site is defined by a colon separated list of strings in square brackets. A site section ends by another site or a set of empty brackets.  +Elements within sites in //Tseries// are usually inactive, the parser will ignore them, unless the user starts //Tseries// with the flag that defines the specific site ( the -S flag). A site is defined by a colon separated list of strings in square brackets. A site section ends by another site or a set of empty brackets.  
  
 <code> <code>
Line 82: Line 83:
 </code> </code>
  
-Basically the server is defined as “meat.com”, if one wants to use the “banana.com” server, one have to start tseries by:+Basically the server is defined as “meat.com”, if one wants to use the “banana.com” server, one have to start //Tseries// by:
  tseries -S FRUIT   tseries -S FRUIT 
  
-To use potato.com in this example, one can start tseries either with “ -S VEGETABLES” or      “-S OTHERS”. This server is valid for for both flags.+To use potato.com in this example, one can start //Tseries// either with “ -S VEGETABLES” or      “-S OTHERS”. This server is valid for for both flags.
  
 ==== Sections ==== ==== Sections ====
  
 Sections are defined by chevrons like ''“<Path>”''. A section is valid until the next section starts. Anything in tseries.ctl is organised in sections from the beginning of the first section. Entities written before the first section starts are pushed into a hash table and can be used freely as substitutes through the entire setup file. Sections are defined by chevrons like ''“<Path>”''. A section is valid until the next section starts. Anything in tseries.ctl is organised in sections from the beginning of the first section. Entities written before the first section starts are pushed into a hash table and can be used freely as substitutes through the entire setup file.
 +^ Token ^ Description ^
 +| nowTime | this special token can be used to generate a formatted string from the clock like ''nowTime=%d-%m'' |
 +
  
 === SECTION: <Path> === === SECTION: <Path> ===
Line 96: Line 100:
 | **Etc**    | Path to find basic configurations | | **Etc**    | Path to find basic configurations |
 | **Images** | Path to find images used in diagrams, like weather symbols | | **Images** | Path to find images used in diagrams, like weather symbols |
-| **Lang**   | Path to find language files, tseries looks for  tseries_XX.qm files in this directory, where XX is the country code.  .qm files are generated by the the Qt linguist tool. |+| **Lang**   | Path to find language files, //Tseries// looks for  tseries_XX.qm files in this directory, where XX is the country code.  .qm files are generated by the the Qt linguist tool. | 
 +| **Styles** | Path to find stylefiles in tsDiagrams.def |
  
  
Line 102: Line 107:
  
 ^ Token ^ Description ^ ^ Token ^ Description ^
-| **Defs**      | The diagram definition file | +| **Defs**      | The diagram definition file (tsDiagrams.def) | 
 | **Configure** | Autogenerated File to store configuration (like window size, language etc) from  the GUI. | | **Configure** | Autogenerated File to store configuration (like window size, language etc) from  the GUI. |
 | **WeatherSymbols** | The weather symbol definition file | | **WeatherSymbols** | The weather symbol definition file |
-| **stdImage**       | Image to send to diana to show stations on the map | +| **stdImage**       | Image to send to [[https://diana.wiki.met.no/doku.php|Diana]] to show positions on the map | 
-| **finImage:  +| **finImage**       | Image to display in [[https://diana.wiki.met.no/doku.php|Diana]] when the “find” button is triggered | 
-Image to display in diana when the “find” button is triggered +| **iconImage**      | The //Tseries// icon | 
-iconImage:  +| **baseFilter**     | A filter file. By using the filter, //Tseries// will only display positions defined in the filter. The filter can be altered and saved locally by the user. | 
-The tseries icon +| **wdbBookmarks**      | In [[https://wdb.wiki.met.no/doku.php|WDB]] mode one can store local bookmarks (positions) into this file | 
-baseFilter: +| **fimexBookmarks**    | In  [[fimex:start|FIMEX]]  mode one can store local bookmarks (positions) into this file | 
-A filter file. If you use the filter, tseries will only display stations defined in the filter. The filter can be altered and saved locally by the user. +| **commonBookmarks** | A file with common bookmarks, valid for all users |
-Bookmarks: +
-In WDB mode you can add your own bookmarks (stations). They will be saved in this file +
-commonBookmarks:  +
-A file with bookmarks given by your company, valid for all users+
  
 +=== SECTION: <fimex> ===
 +^ Token ^ Description ^
 +| **FimexStreamTypes** | List of streamtypes that will be read by  [[fimex:start|Fimex]] , seperated by colon  ''netcdf : ncml'' |
  
  
-<Server> +=== SECTION: <WDB> === 
-The server section is used to define the connection to diana via coserver+^ Token ^ Description ^ 
 +| **Host**  | The WDB host | 
 +| **User**  | The WDB User | 
 +| **busymovie** | Animated gif to display that the server is busy - caching | 
 +| **readtime**  | If a request takes longer than readtime, the cache option appears ( in milliseconds ) | 
 +| **maxRecord **| Cutoff for records in bookmarks |
  
-Client:  
-What application is the target (Diana) 
-Name:  
-What name is sendt to the Client 
-Command:  
-What command is coserver using 
  
-<Streams> 
-The streams section is parsed by an older system, the pets graphical engine, on which 
-tseries is build. 
-All data input from HDF files is defined here, always the same way. 
  
-A new model starts with a collection name, this is more for backwards-compatibility, +=== SECTION: <klima>=== 
-these values are not used by tseries+^ Token ^ Description ^ 
 +| **url** | base URL for the klima requequest | 
 +| **maxDistance** | max distance to an observation in km (default=50) | 
 +| **maxObservationLength** | how many hours to look into the past (default=300) |
  
 +
 +
 +
 +=== SECTION: <Server> ===
 +The server section is used to define the connection to [[https://diana.wiki.met.no/doku.php|Diana]] via coserver
 +
 +^ Token ^ Description ^
 +| **Client**  | Name of the Client ([[https://diana.wiki.met.no/doku.php|Diana]]) |
 +| **Name**    | Name that is sendt to the Client |
 +| **Command** | Command to start coserver |
 +
 +=== SECTION: <Streams> ===
 +
 +The streams section is parsed by an older system, the pets graphical engine, on which
 +//Tseries// is build.
 +All data input from HDF files and  [[fimex:start|Fimex]]  streams is defined here, always the same way.
 +
 +A new model starts with a collection name, this is kept for backwards-compatibility,
 +these values are not used by //Tseries//
 +<code>
 CollectionName=ECMeteogrammer CollectionName=ECMeteogrammer
 PreferredDiagram=Meteogram PreferredDiagram=Meteogram
 InitialOpen=0 InitialOpen=0
 +</code>
  
-In a collection, any datafile has to be registered the following way+In a collection, any hdf/fimex file has to be registered the following way
  
-DataFile: +== A HDF/ASCII Stream == 
-The hdf file +^ Token ^ Description ^ 
-DataDescription:  +| **DataFile**        | The HDF file | 
-The data description. A hdf file can contain several streams. You have to find the exact stream name in the file (when in doubt use vshow). The data description is used to define values in the diagram definition. +| **DataDescription** | The data description. A hdf file can contain several streams. You have to find the exact stream name in the file (when in doubt use vshow). The data description is used to define values in the diagram definition. (tsDiagrams.def) | 
-DataType:  +| **DataType** | HDF or ASCII | 
-HDF or ASCII +| **Contents** | What parameter are defined in the file, x means any.  The string is separated into four sections: Parameter,level,stream,runtime \\ ''x,x,ECMWF,12'' – means: All parameters from ECMWF, 12 \\ ''x,x,ECMWF,x'' - All parameters from ECMWF, all times |
-Contents: +
-What parameter are defined in the file, x means any.  The string is separated into four sections: Parameter,level,stream,runtime +
-x,x,ECMWF,12 – means: All parameters from ECMWF, 12 +
-x,x,ECMWF,x -All parameters from ECMWF, all times+
  
  
 +== A FIMEX Stream ==
 +^ Token ^ Description ^
 +| **DataFile**        | The datafile or URL (opendap) - use of glob is possible  |
 +| **DataDescription** | The data description. Just a string to connect this stream to the diagram definition. (tsDiagrams.def)  |
 +| **DataType** | [ type : tag ] type has to be defined in fimexStreamTypes, tag is optional. if no tag is given, tag=type. Tag is used to connect the parameterdescription to this stream  |
 +| **Contents** | Not really used in Fimexstreams  |
 +| **DataConfig** | Connect a  [[fimex:start|Fimex]]  config file (xml) to this stream  |
 +
 +
 +=== SECTION: <wdbParameter> ===
 +
 +This section maps wdb parameters to tseries parameters
 +
 +<code>
 +
 +# tseries parameter  = <wdb parameter> | <height> < height name>  : <scale> 
 +MSLP,0,x,x,APP=  air pressure at sea level               | 0   height above ground             :/100
 +RR,0,x,x,APP=    lwe precipitation rate                  | 0   height above ground
 +TT,0,x,x,APP=    kalman air temperature                  | 2   height above ground             :-273.15
 +UU,0,x,x,APP=    x wind                                  | 10  height above ground             :*1.94384
 +</code>
 +
 +
 +=== SECTION:<WDBVECTORFUNCTIONS> ===
 +connect two parameters to a vector( to rotate them into a greografic grid)
 +<code>
 +UU,0,x,x,x :VV,0,x,x,x
 +</code>
 +
 +
 +
 +
 +=== SECTION: <klimaparameter> ===
 +
 +<code>
 +# tseries parameter = klimaparameter
 +TT_O,0,x,OBS,x=TA 
 +MSLP_O,0,x,OBS,x=PR 
 +QNH_O,0,x,OBS,x=PH
 +
 +</code>
 +
 +=== SECTION: <klimanormals> ===
 +<code>
 +# tseries parameter = klimaparameter
 +# for these parameters, tseries has to build a timeline
 +TAM,0,x,OBS,x=TAM
 +TANM,0,x,OBS,x=TANM
 +TAXM,0,x,OBS,x=TAXM
 +</code>
 +
 +=== SECTION: <fimexParameters> ===
 +
 +
 +
 +<code>
 +
 +tag       = Given at the fimexstream definition  (DataType : Tag)
 +fimexname = Request parametername
 +Unit      = Udunits string
 +extradim  = Predefined dimensions are time and position, height or similar has to
 +            be defined her for this particular parameter
 +
 +# tseries parameter   = tag | fimexname                | Unit | extradim1 start1 len1 | extradim2 ...
 +#
 +#
 +
 +
 +MSLP,x,x,x = netcdf | air_pressure_at_sea_level         | hPa      | height 0 1
 +TT,x,x,x   = netcdf | air_temperature_2m                | Celsius
 +UU,x,x,x   = netcdf | x_wind_10m                        | kt
 +
 +# with a defined RRAC, tseries knows automatically how to extract RR from it
 +RRAC,x,x,x = netcdf | precipitation_amount_acc          | kg/m^2
 +# Postprocessed temperature - alias...
 +TTPP,x,x,x = netcdf | air_temperature_2m                | Celsius
 +
 +## Wrf data
 +
 +MSLP,x,x,x = wrf | air_pressure_at_sea_level      | hPa     
 +TT,x,x,x   = wrf | T2                             | Celsius
 +UU,x,x,x   = wrf | U10                            | kt  | 
 +VV,x,x,x   = wrf | V10                            | kt  | 
 +
 +</code>
 +
 +
 +===== The Diagram definition file – tsDiagrams.def=====
  
-The Diagram definition file – tsDiagrams.def 
 The Diagram definition file ties the streams to the actual diagram styles. One model input can appear in several diagrams, as well as several different models can use the same diagram type (like a meteogram). It is also possible to use one parameter from a defined stream into a certain diagram that is used by another stream. An example is the use of wind speed from an atmospheric model into a wave-diagram. The Diagram definition file ties the streams to the actual diagram styles. One model input can appear in several diagrams, as well as several different models can use the same diagram type (like a meteogram). It is also possible to use one parameter from a defined stream into a certain diagram that is used by another stream. An example is the use of wind speed from an atmospheric model into a wave-diagram.
-Tseries builds its User interface based on this file. A stream appears first in the menus when it is defined here. If you want to remove a streams from tseries, you have to remove it from this file as well. Otherwise it will appear as an empty entry in the menus.+//Tseries// builds its User interface based on this file. A stream appears first in the menus when it is defined here. If you want to remove a streams from //Tseries//, you have to remove it from this file as well. Otherwise it will appear as an empty entry in the menus.
  
-The [models] section +===The [models] section=== 
-Any model have to be defined in the models section, it also allows to change the display name of the model in the diagrams. The key has to be equal the stream name from tseries.ctl like+All Models have to be defined in the models section, here one can change the display name of the model in the diagrams. The key has to be equal the stream name from tseries.ctl.
  
 +Example:
 +<code>
  ECMWF=Ecmwf  ECMWF=Ecmwf
-  +</code>
-ECMWF is the name from tseries.ctl, and basically the stream definition In the HDF file,  Ecmwf will be displayed in the menus+
  
-The Diagrams+ECMWF equals the DataDescription from tseries.ctl, Ecmwf will be displayed in the //Tseries// GUI menus 
 + 
 + 
 +=== The Diagrams ===
 Each diagram definition connects some parameters from some models to a style. A style can be used several times in different contexts. For instance is the S-meteogram (symbol meteogram) a diagram that uses the meteogram style, but it has also the weather parameter (WW) as input. Each diagram definition connects some parameters from some models to a style. A style can be used several times in different contexts. For instance is the S-meteogram (symbol meteogram) a diagram that uses the meteogram style, but it has also the weather parameter (WW) as input.
 Each diagram defintion starts with the [DIAGRAM] keyword and ends with the [ADD] keyword. Each diagram defintion starts with the [DIAGRAM] keyword and ends with the [ADD] keyword.
  
 +<code>
 Examples: Examples:
  
Line 178: Line 289:
 NAME=Meteogram NAME=Meteogram
 # The connected style file # The connected style file
-STYLEFILE=/usr/share/tseries/5.3/style/style.meteogram+STYLEFILE=meteogram.style
 # The streams connected to this diagram # The streams connected to this diagram
 [LEGALMODELS] [LEGALMODELS]
Line 184: Line 295:
 MODEL=HARMONIE_2.5km MODEL=HARMONIE_2.5km
  
-# modelindependent means, that these parameters will be taken from # all models, if available+# Modelindependent = These parameters will be taken from  
 +# all models, if available 
 [MODELINDEPENDENT] [MODELINDEPENDENT]
 PARAM=UU,x,x,x PARAM=UU,x,x,x
Line 192: Line 305:
 [END] [END]
  
-# modelspecific means that these parameters are only used if they # come from the specified model. +# Modelspecific = These parameters are only used if they come from the specified model. 
-# modflspecifi values are not necessary part of the legalmodels. +# Modelspecific values are not necessary part of the legalmodels. 
 # If they are not defined there, they will not occur in the menu # If they are not defined there, they will not occur in the menu
  
Line 207: Line 320:
  
 [ADD] [ADD]
 +</code>
  
- +====Styles====
-Styles+
 Styles are defined in stylefiles. These are connected to data by tsDiagrams.def. Styles are defined in stylefiles. These are connected to data by tsDiagrams.def.
 By altering the stylesfiles you can control colors, line and object types in the diagram. By altering the stylesfiles you can control colors, line and object types in the diagram.
 There are hundreds of different types in a stylefile.  You have to start with an existing stylefile and reduce that given stylefile until it fits your purpose. A style starts with the definition of the standard values: like default patterns, background color for the diagram etc. There are hundreds of different types in a stylefile.  You have to start with an existing stylefile and reduce that given stylefile until it fits your purpose. A style starts with the definition of the standard values: like default patterns, background color for the diagram etc.
  
 +
 +<code>
 #================================================================== #==================================================================
 #  # 
Line 272: Line 387:
 [DEFAULT] [DEFAULT]
  
 +</code>
  
 Then you have to define axes Then you have to define axes
  
 +<code>
 first at least one x-axis first at least one x-axis
  # --------------------------------  # --------------------------------
Line 287: Line 404:
 minSkipX= 15 minSkipX= 15
 [ADD] [ADD]
 +
 +</code>
  
 And then several y-axes. A curve in the diagram is connected to an axis. If you want to display, for instance several temperatures, you have to create a temperature axis. Then you have to connect the curves to that axis. By that it is guaranteed that the curves are scaled correctly to each other. Each axis has an unique identifier (y-axis-id/yaid). Yaid is used to connect parameters to the axis. And then several y-axes. A curve in the diagram is connected to an axis. If you want to display, for instance several temperatures, you have to create a temperature axis. Then you have to connect the curves to that axis. By that it is guaranteed that the curves are scaled correctly to each other. Each axis has an unique identifier (y-axis-id/yaid). Yaid is used to connect parameters to the axis.
  
 +
 +<code>
  # ----------------------------  # ----------------------------
 # Yaxis (T2m) # Yaxis (T2m)
Line 310: Line 431:
 patternInColour=TRUE patternInColour=TRUE
 [ADD] [ADD]
 +</code>
    
 With axis in place, you have to define a parameter and connect it to it. In this case, the curve is presented in 2 different colors, one for -100 to 0 degrees and one for 0-100 degrees.  With axis in place, you have to define a parameter and connect it to it. In this case, the curve is presented in 2 different colors, one for -100 to 0 degrees and one for 0-100 degrees. 
  
 +<code>
  [NEW]  [NEW]
 type=            LINE type=            LINE
Line 327: Line 449:
 patternInColour= FALSE patternInColour= FALSE
 [ADD] [ADD]
 +</code>
 +
 +===Valid Types:===
 +There are several types in //Tseries// that can be used by the different elements. 
 +
 +====Colors====
 +
 +{{:tseries:pets_colors.png|}}
 +
 +
 +
 +^ Fillpatterns     ^ 
 +| DIAGRIGHT        |         
 +| DIAGLEFT     | 
 +| DIAGCROSS    | 
 +| HORIZONTAL    | 
 +| VERTICAL     | 
 +| SHORIZONTAL    | 
 +| SVERTICAL    | 
 +| SQUARE       | 
 +| SOLID     | 
 +
 +
 +^ Linestyle    ^ 
 +| DASHED           | 
 +| DASHDOTTED       | 
 +| DASHDASHDOTTED   | 
 +| DOTTED    | 
  
  
-Valid types: 
-There are several types in tseries that can be used by the different elements.  
-Colors: 
-BLACK          
-BLUE           
-GREEN          
-CYAN           
-RED            
-MAGENTA        
-YELLOW         
-WHITE          
-GREY25         
-GREY40         
-GREY45         
-GREY50         
-GREY55         
-GREY60         
-GREY65         
-GREY70         
-GREY75         
-GREY80         
-GREY85         
-GREY90         
-GREY95         
-MIST_RED       
-MIST_GREEN     
-MIST_BLUE      
-DARK_GREEN     
-BROWN          
-ORANGE         
-PURPLE         
-LIGHT_BLUE     
-DARK_YELLOW    
-DARK_RED       
-DARK_BLUE      
-DARK_CYAN      
-DARK_MAGENTA   
-MIDNIGHT_BLUE  
-DNMI_GREEN     
-DNMI_BLUE      
-RUST_RED       
-DAWN_RED       
-SUN_YELLOW     
-SPRING_GREEN   
-IRR_GREEN      
-MOSS_GREEN     
-GRASS_GREEN    
-THUNDER_GREY   
-SEA_BLUE       
-SKY_BLUE       
-ICE_BLUE       
-GLACIER_WHITE  
-RAIN_GREY      
-IVORY          
-DARK_IVORY     
-BLUEGREY       
-GREYBROWN      
-OLIVE          
-MUDDYGREEN     
-GREYBLUE       
-DARK_BLUEGREY  
-DARKOLIVE      
-RED_YELLOW     
-YELLOW_RED     
  
-Fillpatterns 
-DIAGRIGHT  
-DIAGLEFT   
-DIAGCROSS  
-HORIZONTAL 
-VERTICAL   
-SHORIZONTAL 
-SVERTICAL  
-SQUARE     
-SOLID   
-Linestyle 
-DASHED          
-DASHDOTTED      
-DASHDASHDOTTED  
-DOTTED  
  • tseries/technical.1390373984.txt.gz
  • Last modified: 2022-05-31 09:23:29
  • (external edit)