"unknown psLib error" when running warptool

[jester@…]

I need to learn how to use the warp.pro things...

But before I asked someone about that, I wanted to try simply running warptool by hand again, and this happened:

(ipp001:jester/stripe82/coadd) jester% warptool -runone -mode warp -workdir /data/ipp001.0/jester/stripe82/coadd/run_ipp/ -cam_id 1
warp_id S64 1
mode STR warp
state STR reg
workdir STR /data/ipp001.0/jester/stripe82/coadd/run_ipp/
dvodb STR NULL
registered UTC 2007-08-22T23:12:13Z

-> p_psDBRunQueryPrepared (psDB.c:893): unknown psLib error

Failed to execute prepared statement. Error: Cannot add or update a child row: a foreign key constraint fails (jester/warpInputExp, CONSTRAINT warpInputExp_ibfk_2 FOREIGN KEY (cam_id) REFERENCES camProcessedExp (cam_id))

-> psDBInsertRows (psDB.c:598): unexpected NULL found

insert failed

-> psDBInsertOneRow (psDB.c:568): unknown psLib error

Failed to insert row.

-> addinputexpMode (warptool.c:327): unknown psLib error

database error

-> runoneMode (warptool.c:232): unknown psLib error

failed to add cam_id to warpRun

Before running this, I tried to just say
warp.on
in pantasks (after injecting, register, chip, cam), maybe there was some interference? I'm saying that because register.imfile.load and exp.load keep adding new images, as do warp.exp.load and warp.skycell.load, even though I thought I injected the same 51 images as before, and imfile.run and exp.run both stay at 51.

[Paul Price]

I suspect this is due to a new database configuration. If it's quick and easy to regenerate your database state from scratch (following a "pxadmin -recreate"), let's go for that. Otherwise, we can try to dig up the changes so that we can change your database on the fly.

[jester@…]

Humm... just realized that I hadn't actually turned chip and camera on (I thought I had) so the problem was just that there wasn't anything to operate on. This explains the "unexpected NULL".

So the bug is that warptool is not checking that its input exists.

[Paul Price]

I think that's what the foreign key constraints do.