DB_ENTRY
Class keeps information about one, particular database entry (eg. pulse-file),
Definition (constructor)
DB Entry is defined by:
- backend
- user name (eg.
g2bpalak
) - db name (eg.
test
) data version - do we need it (see Open Points)?
create_env(self, user, tokamak, version, silent=False)
→
Open points TBD:
Code Block |
---|
language | py |
---|
title | db_entry constructor |
---|
|
def __init__(self, backendID, db_name, shot, run, userName=$USER) |
Additional "URI-based" constructor will be added in future...
...
Info |
---|
icon | false |
---|
title | Open points |
---|
|
- Data version - to be removed?
|
- Currently it is not used (in every cases fixed to
3 } - Could be specified by future API using URI, if will be need in future.
|
...
-
- SUGGESTION - TO REMOVE from API
|
Create/open/close
All parameters that defines db_entry
are set in constructor, so create, open, close
will have no arguments
Code Block |
---|
language | py |
---|
title | db_entry create/open/close |
---|
|
def create(self)
def open(self)
def close(self) |
Info |
---|
icon | false |
---|
title | Open points |
---|
|
- "silent" - a parameter to make LL quiet
- An additional method setVerbosity will be added
|