[Babase] VIV sexskin not uploading due to missing mdate

Karl O. Pinc kop at meme.com
Fri May 29 18:31:38 EDT 2009


On 05/21/2009 12:05:41 PM, Niki Learn wrote:
> -----Original Message-----
> From: babase-bounces at eeblistserv.Princeton.EDU
> [mailto:babase-bounces at eeblistserv.Princeton.EDU] On Behalf Of kfenn
> Sent: Wednesday, May 20, 2009 12:37 PM
> To: The Baboon Database Project
> Subject: [Babase] VIV sexskin not uploading due to missing mdate
> 
> Hi Karl,
> 
> We have a perplexing question relation to uploading sexskin size date
> to
> the SEXSKINS_CYCLES view.
> 
> One female, VIV, cycled in June of 2007 but shut down until October of
> 
> the same year.
> 
> Niki was trying to upload her October sizes and got the following
> error
> message:
> ERROR: Sxid 144307: Cid 27583: 2007-10-17: No Mdate found for this
> cycle
> 
> OK, fair enough.  We thought she was pregnant in June and entered her
> June Ddate into Pregs as a conceive date.
> 
> However, in the following update period, I removed her pregnancy from
> PREGS when Jeanne decided this was not a real pregnancy.

I think Tabby nailed the problem: The automatic mdates were
not updated when a pregnancy (PREGS row) was deleted.

I believe I have (finally) fixed this.  It would be good
if somebody besides me would double check the fix by
deleting a pregnancy and watching what happens to the
automatic Mdates.

The next step is to fix the database. Either we need to
remember all the pregnancies that have been deleted
and manually make changes or we need to schedule a time
for me to temporarily turn off all the data validation
and rebuild the automatic Mdates.
> 
> I missed uploading a ddate back in April 2007 for a female named WEN.
> 
> She had a normal cycle right after that and I was allowed to skip the
> ddate in April and upload the subsequent cycle without the system
> throwing an error.  There was no gap in observation....any idea why I
> got away with this?

I think it's due to footnote 58:
CYCPOINTS
https://papio.biology.duke.edu/babase_system_html/ch03s10.html

[58] The system allows the condition to occur to provide an opportunity  
to insert a new Mdate, Ddate, Tdate aggregate -- a new cycle -- into  
the middle of a period of observation. One of these dates must be  
inserted first, breaking, for the moment, the pattern of cycling -- the  
repetition of the Mdate, Ddate, Tdate sequence.

What's supposed to happen is that we've error checks to run to check
for conditions that that cannot be checked for as data is entered.
It's that big list of SQL queries.  We're not running them
automatically.

> 
> Thanks,
> Tabby
> 
> 
> Niki writes:
> 
> FYI, today WEN has an mdate for the cycle in question - guess it just
> took a
> while for it to be automatically generated after we added her ddate.

That does not sound right.  When a Ddate goes in there should always
be an automatic Mdate right away.  Did you see a time when there was
a Ddate but not an automatic Mdate?

Karl <kop at meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein



More information about the Babase mailing list