You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

1. DB_ENTRY (AL_ENTRY?)

Class keeps information about one, particular  database entry (eg. pulse-file)


Class structure:

db_entry class hierarchy


AL_ENTRY , DB_ENTRY - any better names?

1.1. Definition (constructor)

AL Entry  is defined by:

  • backend
  • user name (eg. g2bpalak )
  • db name (eg. test )
  • data version - do we need it (see Open Points)?
  • shot
  • run
db_entry constructor
def __init__(self, backendID, db_name, shot, run, userName=$USER)



Additional "URI-based" constructor will be added in future...

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

1.2. Create/open/close

All parameters that defines db_entry  are set in constructor, so create, open, close will have no arguments

db_entry create/open/close
def create(self)
def open(self)
def close(self)


Open points

  • "silent" - a parameter to make LL quiet
    • An additional method setVerbosity will be added

1.3. Get IDS


IDS GET
def get(self, idsName, occurrence = 0) # idsName (e.g. 'equilibrium')
	return ids


IDS PUT
def put(self, ids, occurrence = 0)

1.4. Any other method is needed to ba added to db_entry class?

getTime vector?




  • No labels