[Issue 194: updates to scheduler and testing of it (205)](https://github.com/al-niessner/DAWGIE/commit/d6dbabeae5275c22eda87a40703f9577deba2d88)
*Author*: al-niessner
*Date*: Wed, 28 Jun 2023 13:11:38 -0700
* first steps in fix
Improved documentation so the next time this code is looked at or reviewed,
it can go faster. It works out since what it does is no longer in my head and
this documentation represents what I found difficult to decipher.
* make all test runnable independently
Having to wait for all the tests to run was slowing down development. Wrapped it into this branch because this work is required sooner rather than later.
* fixed previous test that caused the problem
Turns out that promotion engine tests set something that caused this test to fail. Implemented a tearDownClass() to undo what it set. Fixed the tests when they all run.
[add default value to help (202)](https://github.com/al-niessner/DAWGIE/commit/ab0c935eb4737da626819ddef0cf4aad172335b8)
*Author*: al-niessner
*Date*: Wed, 3 May 2023 20:51:19 -0700
Co-authored-by: Al Niessner <Al.Niessnerxxx.xxx>
[stronger check for true (201)](https://github.com/al-niessner/DAWGIE/commit/2e53276c50600e4fee8c4132177a656db9f65edb)
*Author*: al-niessner
*Date*: Wed, 3 May 2023 17:29:35 -0700
[add more context to the error message (200)](https://github.com/al-niessner/DAWGIE/commit/0f7eae94137d48f4cc2ccd507bdfc18cbecf6ef0)
*Author*: al-niessner
*Date*: Wed, 3 May 2023 16:12:16 -0700
[Issue 189: redo shelf to shelve (193)](https://github.com/al-niessner/DAWGIE/commit/0041df5950ec5c965b72489acbc54907b44b52b0)
*Author*: al-niessner
*Date*: Wed, 3 May 2023 15:45:29 -0700
* rewriting shelf
Changed a bunch of names (not all) from shelf to shelve while doing the rewrite just to make it match. It makes it much nicer in understanding the mapping of databases.
Cleaned up post2shelve to use the new shelve tables that account for versions.
Still had a bit of shelf laying about that testing found. Cleaned it up and changed some of the test harness to fit the new shelve.
The bulk of the changes came when the unit tests started running. It was here that most of the type changes and the whole concept of the db changes worked itself out.
[renamed redirect to retarget (192)](https://github.com/al-niessner/DAWGIE/commit/3f55e9151547aba03cb00c6288648043ee9ca320)
*Author*: al-niessner
*Date*: Mon, 19 Dec 2022 08:43:59 -0800
* renamed redirect to retarget
Fixed 190 as well since it was in the same location and easy.
Renamed the functions and checked that all connections still work. However, updating the past items still needs to be done.
* retarget implementation for postgres
Did the simplest/hardest all at once. Create duplicate target entries for upstream items by simply walking the prime table. It is a little lazy and it does the latest rid for a task and algorithm. If state vectors and values are well behaved as in defined at algorithm instantiation like they are supposed to be then this shortcut is sufficient.
Leaving shelf for when it is made to really behave like postgres.
* informational updates
Cleaned up error and log message. Changed the look of retarget() names.
[Update __init__.py](https://github.com/al-niessner/DAWGIE/commit/ee6a4e2f3c502d35535d0af95bd72c27978f084f)
*Author*: al-niessner
*Date*: Thu, 13 Oct 2022 14:01:57 -0700
[issue_186: maybe fix timelines (188)](https://github.com/al-niessner/DAWGIE/commit/fe889944d02b3720297425133b069e4e7a7b762f)
*Author*: al-niessner
*Date*: Thu, 13 Oct 2022 13:14:05 -0700
* maybe fix timelines
Could not exactly replicate the error in the log file but found a simple error and repaired it. Given how algorithm and sv PKs work, it is necessary to allow multiples and then work with the latest in the database (largest primary table PK).
* fixed timelines
The notebook page was running with the older psycopg2 which worked. Moved to the correct psycopg (3.1.9) and duplicated the error. Corrected it code using fetchall() as it now returns a list of tuples.
[Issue 185: infinite recursion (187)](https://github.com/al-niessner/DAWGIE/commit/5df9aff2210baa4cf1a943f120254d089c4ee9bc)
*Author*: al-niessner
*Date*: Fri, 7 Oct 2022 14:34:29 -0700
* change to show problem
* fix for infinite recursion
[Issue 183: extend interface (184)](https://github.com/al-niessner/DAWGIE/commit/557b52453e70e7476d0ecb0bf5ec498579f89fbe)
*Author*: al-niessner
*Date*: Fri, 7 Oct 2022 12:37:16 -0700
* add two helper functions to the API
It should be simple to add new targets. It is simple to use an Analyzer to compute all of the desireable targets. It is not easy to have that target added to the database without doing some dawgie gymnastics. Added dawgie.db.add() to remove these gymnastics from the AE.
The idea of sub-targets has come up. In the view of the AE some targets may have sub processing channels that are better shown with sub-target names like A(b) where A is the primary target and b is the sub-target. In this sense, algorihm foo() now works on sub targets A(b) and A(c) independently and in parallel rather than sequentially.
* add two helper functions to the API
It should be simple to add new targets. It is simple to use an Analyzer to compute all of the desireable targets. It is not easy to have that target added to the database without doing some dawgie gymnastics. Added dawgie.db.add() to remove these gymnastics from the AE.
The idea of sub-targets has come up. In the view of the AE some targets may have sub processing channels that are better shown with sub-target names like A(b) where A is the primary target and b is the sub-target. In this sense, algorihm foo() now works on sub targets A(b) and A(c) independently and in parallel rather than sequentially.
* update testing
The change in dawgie.db requires testing to show that any implementation for it works as expected.
* implementation of dawgie.db.add()
Post dawgie.db.post and dawgie.db.shelf required updating. Both have implementations and the postgres has been tested.
[repair dawgie.db.post.trace() (182)](https://github.com/al-niessner/DAWGIE/commit/32e3ce209095337c154b000b3573ba8ff08114be)
*Author*: al-niessner
*Date*: Fri, 19 Aug 2022 16:47:49 -0700
The original code simply found the max for each of the different version values (design, impl, bugfix). The function needs to compute the max in a cascading for such that bugfix.max() is constrained by impl.max() which is then constrained by design.max() so that 1.1.7, 1.9.3 and 2.4.1 returns 2.4.1 and not 2.9.7. The latter is what the prefix code was doing and now the former is correctly returned with these changes.
[handle as info() not error() (180)](https://github.com/al-niessner/DAWGIE/commit/981d5ef72b7c80f7738d25c0df5dd304ee1fae2b)
*Author*: al-niessner
*Date*: Fri, 19 Aug 2022 16:21:23 -0700
Changed the logging from exception() to info() because these are allowed exceptions that allow a success status despite no output being generated. It means there is a data error but nothing that a stack trace helps with at least.