Difference: DCSRequirementsDB (1 vs. 20)

Revision 20
23 Jun 2010 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 35 to 35
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(16), description TEXT(255),
Changed:
<
<
contact INT(3)
>
>
contact INT(3), alt_contact INT(3)
  );
Line: 115 to 116
  name VARCHAR(60), email VARCHAR(60), phone VARCHAR(20),
Added:
>
>
alt_phone VARCHAR(20),
  institute INT(3), homepage VARCHAR(120), registered TINYTEXT
Revision 19
03 Feb 2010 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 58 to 58
 
mysql> CREATE TABLE Units (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Added:
>
>
quantity VARCHAR(32),
  name VARCHAR(24),
Deleted:
<
<
parameter VARCHAR(32),
  description TEXT(64) );
Revision 18
11 Dec 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 128 to 128
  vendor VARCHAR(60), name VARCHAR(60), description VARCHAR(60),
Added:
>
>
connectivity VARCHAR(60),
  platform CHAR(20),
Added:
>
>
documentation VARCHAR(100),
  supported_by VARCHAR(60) );
Revision 17
10 Dec 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 43 to 43
  mysql> CREATE TABLE Types ( id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(20),
Changed:
<
<
description TEXT(50);
>
>
description TEXT(50)
  );
Changed:
<
<
mysql> CREATE TABLE Pv_names (
>
>
mysql> CREATE TABLE Parameters (
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(32), description VARCHAR(60)
Line: 60 to 60
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(24), parameter VARCHAR(32),
Changed:
<
<
description TEXT(64);
>
>
description TEXT(64)
  );
Line: 71 to 71
  mysql> CREATE TABLE ProcessVariables ( id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, subgroup INT(3),
Changed:
<
<
pv_name INT(11),
>
>
parameter INT(11),
  unit INT(3), type INT(3), channels INT(5),
Line: 112 to 112
 
mysql> CREATE TABLE Contacts (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
firstname VARCHAR(60), lastname VARCHAR(30),
>
>
name VARCHAR(60),
  email VARCHAR(60), phone VARCHAR(20),
Changed:
<
<
institute INT(3)
>
>
institute INT(3), homepage VARCHAR(120), registered TINYTEXT
  );
Revision 16
25 Nov 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 126 to 126
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, vendor VARCHAR(60), name VARCHAR(60),
Changed:
<
<
driver VARCHAR(60),
>
>
description VARCHAR(60),
  platform CHAR(20), supported_by VARCHAR(60) );
Revision 15
14 Apr 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 6 to 6
 

Changed:
<
<

Responsibles

>
>

Status

 
Changed:
<
<
Responsible for this implementation will be JaroslawSzewinski and DanProtopopescu. The system should be preferably fully functional by 15/04/2008.

Current status: Merging code implementations. Partly functional system can be tested at: http://nuclear.gla.ac.uk/DCS/
>
>
Current status: System up and running at: http://nuclear.gla.ac.uk/DCS/
 

Components

Changed:
<
<
The MySQL database is located on a Linux machine, running a PHP-enabled Apache server.
>
>
The MySQL database is located on a Linux machine, running a PHP-enabled Apache server. The UI is custom-written. Everything is modular.
 

Structure

Line: 61 to 59
  mysql> CREATE TABLE Units ( id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(24),
Changed:
<
<
value VARCHAR(32),
>
>
parameter VARCHAR(32),
  description TEXT(64); );
Changed:
<
<
In this table we could have items like unit, type referred by integer id and cross-query the above tables or direct, by the VARCHAR name. I would opt for the latter for better readability.
>
>
In this table, items like unit, type are referred by an integer id and cross-queried from the above tables. This ensures standardization.
 

mysql> CREATE TABLE ProcessVariables (
Line: 136 to 134
 

Access restrictions

Changed:
<
<
Administrative access (SSH to the server and to the DB itself) is restricted to the responsibles. Access to insert/update data into tables is restricted to registered users, with registration and authentication via the web interface.
>
>
Administrative access (SSH to the server and to the DB itself) is restricted to the developers. Access to insert/update data into tables is restricted to registered users, with registration and authentication via the web interface.
 

Interface

Changed:
<
<
We have a fully custom-written PHP interface and phpMyAdmin for DB administration. The user interface URL is: http://nuclear.gla.ac.uk/DCS/
>
>
We have a fully custom-written PHP interface. The URL is: http://nuclear.gla.ac.uk/DCS/
 

Location

Changed:
<
<
The DB and web interface will be physically located on a server in Glasgow for the initial design and testing period. Both DB and UI are very easy to transport to another server, in case a suitable server could be found at GSI.
>
>
The DB and web interface will be physically located on a server in Glasgow for the initial design and testing period. Both DB and UI are very easy to transport to another server, in case a suitable server could be found at GSI.
 

Present location: http://nuclear.gla.ac.uk/DCS/
Revision 14
09 Apr 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 60 to 60
 
mysql> CREATE TABLE Units (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
name VARCHAR(5), value VARCHAR(20), description TEXT(50);
>
>
name VARCHAR(24), value VARCHAR(32), description TEXT(64);
  );
Revision 13
09 Apr 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 33 to 33
  There are at present 8 tables in the database:
Changed:
<
<
mysql> CREATE TABLE Subdetectors (
>
>
mysql> CREATE TABLE Subgroups (
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(16), description TEXT(255),
Line: 50 to 50
 
Changed:
<
<
mysql> CREATE TABLE sValues (
>
>
mysql> CREATE TABLE Pv_names (
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
name VARCHAR(20)
>
>
name VARCHAR(32), description VARCHAR(60)
  );
Line: 71 to 72
 
mysql> CREATE TABLE ProcessVariables (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
subdetector INT(3), PVname VARCHAR(32),
>
>
subgroup INT(3), pv_name INT(11),
  unit INT(3), type INT(3), channels INT(5),
Revision 12
07 Apr 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Changed:
<
<
A MySQL implementation of a DCS detector requirements database is proposed here, as first proposed in Jarek's talk (attached).
>
>
A MySQL implementation of a DCS detector requirements database is presented here, as first proposed in Jaroslaw Szewinski's talk (attached).
 

Line: 12 to 11
  Responsible for this implementation will be JaroslawSzewinski and DanProtopopescu. The system should be preferably fully functional by 15/04/2008.
Added:
>
>
Current status: Merging code implementations. Partly functional system can be tested at: http://nuclear.gla.ac.uk/DCS/
 

Components

Changed:
<
<
The MySQL database will be located on a Linux machine, running a PHP-enabled Apache server.
>
>
The MySQL database is located on a Linux machine, running a PHP-enabled Apache server.
 

Structure

Changed:
<
<
There are two options:
  • One single database with first column in each table denoting the corresponding subdetector
  • One database per subdetector (might be safer)
The first option has the advantage that is makes easier to obtain cumulated/cross-detector figures of the DCS requirements.
>
>
The implemented structure is one single database DCS_REQ, with eight tables:
 

mysql> CREATE DATABASE DCS_REQ;
Line: 32 to 30
 

Tables

Changed:
<
<
Tentatively, there could be 8 tables in the database:
>
>
There are at present 8 tables in the database:
 

mysql> CREATE TABLE Subdetectors (
Line: 97 to 95
  );
Changed:
<
<
Then some auxiliary tables:
>
>
The auxiliary tables:
 

mysql> CREATE TABLE Institutes (
Line: 137 to 135
 

Access restrictions

Changed:
<
<
During design and implementation the access (SSH to the server and to the DB itself) will be restricted to the responsibles. Access to insert/update data into tables will be restricted to each detector group via the PHP input interface.
>
>
Administrative access (SSH to the server and to the DB itself) is restricted to the responsibles. Access to insert/update data into tables is restricted to registered users, with registration and authentication via the web interface.
 

Interface

Changed:
<
<

Custom written PHP interface and phpMyAdmin for DB administration. A simple demo was set up here: http://nuclear.gla.ac.uk/DCS/interactiveTable.php?name=ProcessVariables
>
>
We have a fully custom-written PHP interface and phpMyAdmin for DB administration. The user interface URL is: http://nuclear.gla.ac.uk/DCS/
 

Location

Changed:
<
<
The DB will be physically located on a server at GSI after an initial design and testing period.
>
>
The DB and web interface will be physically located on a server in Glasgow for the initial design and testing period. Both DB and UI are very easy to transport to another server, in case a suitable server could be found at GSI.

Present location: http://nuclear.gla.ac.uk/DCS/
 

-- DanProtopopescu - 04 Mar 2008
Revision 11
04 Apr 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 152 to 152
  -- DanProtopopescu - 04 Mar 2008

META FILEATTACHMENT attr="" comment="Jaroslaw Szewinski talk at GSI on 03/03/2008" date="1204622611" name="JS18-080303_dcs_database.pdf" path="JS18-080303_dcs_database.pdf" size="49490" user="DanProtopopescu" version="1.2"
Added:
>
>
META FILEATTACHMENT attr="" comment="Jarek's code tarball (first release)" date="1207150634" moveby="DanProtopopescu" movedto="DCS.DCSRequirementsDB" movedwhen="1207332164" movefrom="DCS.WebHome" name="dcs.tar.gz" path="dcs.tar.gz" size="54224" user="DanProtopopescu" version="1.1"
META FILEATTACHMENT attr="" comment="Dan's UI implementation php code tarball (initial release)" date="1207233473" moveby="DanProtopopescu" movedto="DCS.DCSRequirementsDB" movedwhen="1207332197" movefrom="DCS.WebHome" name="code.tgz" path="code.tgz" size="7508" user="DanProtopopescu" version="1.1"
Revision 10
03 Apr 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 37 to 37
 
mysql> CREATE TABLE Subdetectors (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
name VARCHAR(10),
>
>
name VARCHAR(16),
  description TEXT(255), contact INT(3) );
Revision 9
12 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 74 to 74
  mysql> CREATE TABLE ProcessVariables ( id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, subdetector INT(3),
Changed:
<
<
name VARCHAR(20),
>
>
PVname VARCHAR(32),
  unit INT(3), type INT(3), channels INT(5),
Revision 8
11 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 75 to 75
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, subdetector INT(3), name VARCHAR(20),
Changed:
<
<
units INT(3),
>
>
unit INT(3),
  type INT(3), channels INT(5), nominal_value FLOAT,
Line: 90 to 90
  is_controlled TINYINT, gen_interlock TINYINT, description TEXT(255),
Changed:
<
<
req_person VARCHAR(100),
>
>
contact INT(3),
  hardware VARCHAR(60), lastupdatedby VARCHAR(40), timestamp TIMESTAMP(8)
Revision 7
10 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 39 to 39
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(10), description TEXT(255),
Changed:
<
<
contact_name VARCHAR(100), contact_email VARCHAR(100)
>
>
contact INT(3)
  );

mysql> CREATE TABLE Types (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
name VARCHAR(20)
>
>
name VARCHAR(20), description TEXT(50);
  );
Line: 103 to 103
  mysql> CREATE TABLE Institutes ( id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(60),
Deleted:
<
<
contact VARCHAR(60), email VARCHAR(60),
  address VARCHAR(200),
Changed:
<
<
phone VARCHAR(20)
>
>
contact_name VARCHAR(60), contact_phone VARCHAR(20), contact_email VARCHAR(50)
  );
Added:
>
>
People table:
 
Changed:
<
<
mysql> CREATE TABLE People (
>
>
mysql> CREATE TABLE Contacts (
  id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, firstname VARCHAR(60), lastname VARCHAR(30),
Revision 6
10 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 136 to 136
 

Access restrictions

During design and implementation the access (SSH to the server and to the DB itself) will be restricted to the responsibles.
Changed:
<
<
Access to insert/update data into tables will be restricted to each detector grou via the PHP input interface.
>
>
Access to insert/update data into tables will be restricted to each detector group via the PHP input interface.
 

Interface

Changed:
<
<
Custom written PHP interface and phpMyAdmin for DB administration. A simple demo was set up here: http://nuclear.gla.ac.uk/DCS/pvexample.php
>
>
Custom written PHP interface and phpMyAdmin for DB administration. A simple demo was set up here: http://nuclear.gla.ac.uk/DCS/interactiveTable.php?name=ProcessVariables
 

Location

Revision 5
05 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 32 to 32
 

Tables

Changed:
<
<
Tentatively, there could be 8 tables in the database, with separate insert/select permissions.
>
>
Tentatively, there could be 8 tables in the database:
 

mysql> CREATE TABLE Subdetectors (
Revision 4
04 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 61 to 61
 
mysql> CREATE TABLE Units (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
name VARCHAR(20), value CHAR(5)
>
>
name VARCHAR(5), value VARCHAR(20), description TEXT(50);
  );
Line: 116 to 117
  lastname VARCHAR(30), email VARCHAR(60), phone VARCHAR(20),
Changed:
<
<
institute VARCHAR(60)
>
>
institute INT(3)
  );
Line: 140 to 141
 

Interface

Changed:
<
<
Custom written PHP interface and phpMyAdmin for DB administration.
>
>
Custom written PHP interface and phpMyAdmin for DB administration. A simple demo was set up here: http://nuclear.gla.ac.uk/DCS/pvexample.php
 

Location

Revision 3
04 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 25 to 25
 

mysql> CREATE DATABASE DCS_REQ;
Changed:
<
<
mysql> GRANT all PERMISSIONS ON DCS_REQ to dsc_req_db_admin with password ***;
>
>
mysql> GRANT ALL ON DCS_REQ.* TO 'dsc_req_db_admin'@'localhost' IDENTIFIED BY '******'; mysql> FLUSH PRIVILEGES;
 

Line: 37 to 38
  mysql> CREATE TABLE Subdetectors ( id INT NOT NULL PRIMARY KEY AUTO_INCREMENT, name VARCHAR(10),
Added:
>
>
description TEXT(255),
  contact_name VARCHAR(100), contact_email VARCHAR(100) );
Line: 70 to 72
 
mysql> CREATE TABLE ProcessVariables (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
Changed:
<
<
subdetector VARCHAR(10),
>
>
subdetector INT(3),
  name VARCHAR(20),
Changed:
<
<
unit VARCHAR(10), type VARCHAR(20),
>
>
units INT(3), type INT(3),
  channels INT(5), nominal_value FLOAT, range_min FLOAT,
Revision 2
04 Mar 2008 - Main.DanProtopopescu
Line: 1 to 1
 
META TOPICPARENT name="WebHome"

DCS Detector Requirements Database

Line: 30 to 31
 

Tables

Changed:
<
<
There will be 8 tables in the database, with separate read/write permissions. In addition, every table will have a 'lastupdatedby' column to keep better track of changes.
>
>
Tentatively, there could be 8 tables in the database, with separate insert/select permissions.

mysql> CREATE TABLE Subdetectors (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
         name VARCHAR(10),
         contact_name VARCHAR(100),
         contact_email VARCHAR(100)
        );

mysql> CREATE TABLE Types (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
         name VARCHAR(20)
        );

mysql> CREATE TABLE sValues (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
         name VARCHAR(20)
        );

mysql> CREATE TABLE Units (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
         name VARCHAR(20),
         value CHAR(5)
        );

In this table we could have items like unit, type referred by integer id and cross-query the above tables or direct, by the VARCHAR name. I would opt for the latter for better readability.
 

mysql> CREATE TABLE ProcessVariables (
Line: 39 to 73
  subdetector VARCHAR(10), name VARCHAR(20), unit VARCHAR(10),
Changed:
<
<
update_frequency INT(6),
>
>
type VARCHAR(20), channels INT(5), nominal_value FLOAT, range_min FLOAT, range_max FLOAT, warn_min FLOAT, warn_max FLOAT, alarm_min FLOAT, alarm_max FLOAT, update_rate INT(6), is_monitored TINYINT, is_controlled TINYINT, gen_interlock TINYINT, description TEXT(255), req_person VARCHAR(100), hardware VARCHAR(60),
  lastupdatedby VARCHAR(40), timestamp TIMESTAMP(8) );
Added:
>
>
Then some auxiliary tables:

mysql> CREATE TABLE Institutes (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
         name VARCHAR(60),
         contact VARCHAR(60),
         email VARCHAR(60),
         address VARCHAR(200),
         phone VARCHAR(20)
        );

mysql> CREATE TABLE People (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
         firstname VARCHAR(60),
         lastname VARCHAR(30),
         email VARCHAR(60),
         phone VARCHAR(20),
         institute VARCHAR(60)
        );

mysql> CREATE TABLE Hardware (
         id INT NOT NULL PRIMARY KEY AUTO_INCREMENT,
         vendor VARCHAR(60),
         name VARCHAR(60),
         driver VARCHAR(60),
         platform CHAR(20),
         supported_by VARCHAR(60)
        );
 

Access restrictions

During design and implementation the access (SSH to the server and to the DB itself) will be restricted to the responsibles.
Added:
>
>
Access to insert/update data into tables will be restricted to each detector grou via the PHP input interface.
 

Interface

Line: 60 to 146
 

-- DanProtopopescu - 04 Mar 2008
Changed:
<
<
META FILEATTACHMENT attr="" comment="Jarek's talk on this topic" date="1204604671" name="JS18-080303_dcs_database.pdf" path="JS18-080303_dcs_database.pdf" size="1353" user="DanProtopopescu" version="1.1"
>
>
META FILEATTACHMENT attr="" comment="Jaroslaw Szewinski talk at GSI on 03/03/2008" date="1204622611" name="JS18-080303_dcs_database.pdf" path="JS18-080303_dcs_database.pdf" size="49490" user="DanProtopopescu" version="1.2"
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding PANDA Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)