[Bio] / BioSimScratch / buildNewBssCatalog.py Repository:
ViewVC logotype

Log of /BioSimScratch/buildNewBssCatalog.py

Parent Directory Parent Directory


Links to HEAD: (view) (download) (as text) (annotate)
Sticky Tag:

Revision 1.5 - (view) (download) (as text) (annotate) - [select for diffs]
Fri Nov 19 23:22:48 2004 UTC (14 years, 10 months ago) by efrank
Branch: MAIN
CVS Tags: HEAD, post-st-migration, post-st-migration2
Changes since 1.4: +1 -1 lines
Diff to previous 1.4
migrate FoundryId to FoundryInfo.

rewrite base object model classes in KahOM and FoundryId to use SchemaTools
   for their data nuggets.

code runs package level test for these two packages successfully.

everything else is now broken.....

we'r ready for the migration.

Revision 1.4 - (view) (download) (as text) (annotate) - [select for diffs]
Tue Jul 13 21:15:07 2004 UTC (15 years, 3 months ago) by efrank
Branch: MAIN
CVS Tags: forRick-14Jul04-0, forRick-14Jul04-1, mass-spec-01, mass-spec-02, sc04-finalDay, sc2004-0, sc2004-1, sc2004-2, sc2004-3, sc2004-4
Changes since 1.3: +1 -1 lines
Diff to previous 1.3
Schema:
	o change size of Function column from 64 to 128.
	  More reasonable size and avoids a crash.
	o RebuldDb...runs all the steps of rebuilding the database.
	o biuldNewBssCatalog:  go to new BssFactory ctor

CatalogServices:
	o remove setFoundryId from DataFactoryBase.  Now expect that info
	  to be in the DB itself and for ctor of derivative to set it.

FaST:
	o Migrate to new DbManager from DBconnect.  Includes moving to
	  new nextSeqVal().
	o Now get fid from database
PyGui:
	o Changed to follow mods above.
	o

Revision 1.3 - (view) (download) (as text) (annotate) - [select for diffs]
Wed May 26 01:38:25 2004 UTC (15 years, 4 months ago) by efrank
Branch: MAIN
Changes since 1.2: +3 -3 lines
Diff to previous 1.2
Lots of work aimed at getting catalog services to work, incorporating
catalog editing into the model editor, and simplifying the api
for going form path to model in hand to work with.

CatalogEntryTop was changed to CatalogEntrBase and made base of CatalogEntry
rather than other way around to break a dependency loop that was causing
python import problems.  CatalogEntry is still the base class to use
for extending to new data factories.

changed open() to return catalogEntry rather than foundryItemKey.  simpler
for the user and more opportunity to encapsulate.

made catalogEntry able to read a recoElem and return it.  all done in
terms of arch abstractions.  this is temorary.  we will add a Navigator
or Manager class and that will be returned from the CatalogEntry rather
than recoElem.  that's becausee Recoelem is just one of many things
that will be present, e.g., conditions data.

PyGui/MainMenuBar.  split out to help stay sane for when that becomes
more complex.

Moved add seed server to menu bar so that right click in catalog panel
coudl be used to pull up catalog editing tools.

Revision 1.2 - (view) (download) (as text) (annotate) - [select for diffs]
Thu Apr 15 14:49:16 2004 UTC (15 years, 6 months ago) by efrank
Branch: MAIN
Changes since 1.1: +18 -4 lines
Diff to previous 1.1
Add setFoundryItem capability to CatalogEntry, implemented in CatalogEntryBss.
Modifications to CreateCatalog to support this, and to support change
in FoundryId so that the basic id is a string, not an int.

Revision 1.1 - (view) (download) (as text) (annotate) - [select for diffs]
Fri Apr 9 14:48:10 2004 UTC (15 years, 6 months ago) by efrank
Branch: MAIN
Modified files:
	adjustments in data sizes and little details
	destroyBss can probably be simplified.

Added files:
	ReloadBssData loads data into an empty database.  It calls
	the other guys to do the work:  Aiba*, glyc*, loadbuchnera*, testCas*

	buildNewBssCatalog.py:  copies data from old style catalog to new.


1. destroyBss                   deletes EVERYTHING
2. sqlplus
        @Rebuild                rebuilds schema.  reloads some reactions etc.
3. ReloadBssData                puts some data back in...OLD style catalog
4. buildNewBssCatalog.py        copies data from old style catalog to new.

This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.

  Diffs between and
  Type of Diff should be a

Sort log by:

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3