Printer friendly version 
 Square Dance Resource Net  (Home)ArticlesCallers and CuersClubsEventsResourcesChoreographyMusicLyricsCeder Chest Definition BooksCeder Square Dance System  (CSDS)Square Rotation Program  (SQROT)Vic Ceder - Square Dance CallerDefinitions of square dance calls and conceptsMore square dance DefinitionsLists of square dance calls and conceptsFrequently Asked QuestionsSquare dance linksLos Olivos Honey BeesBande DéssineesChocolate BarsBeanie BabiesPokémon Trading CardsSend us feedback
FAQs
 
FAQs
 

Ceder Square Dance System (CSDS) ==> Snapshots

Database consistency
I selected the menu item "Sequence / Proofread / Specified" and said "No prompts". One of the error messages I got is:
Sequence C2-96 line 6 -- Call not found:
   HOCUS POCUS
   Hocus Pocus [571]

The sequence I tested is ok in the graphical editor:

 
(This is a test, only),
Heads Pass The Ocean,
Extend The K,
(#formation#)
(Exit: Detour, Those Facing Start Dixie Grand, L.A.),
Hocus Pocus,
Split Counter Rotate 1/4,
Vertical Tag Back To A Wave,
R.L.G.

Any idea what could cause error messages like that where it says "Call not found" but says "[571]" nevertheless ?

Is there a way to check the consistency of the snapshot database or to repair it?

I tried the sequence given above on my machine in both the 'Edit Seq [Graphics]' and the 'Proofread | Specified' sections of the program. It worked fine.

The most probable cause for this error is that there is a problem with the snapshot database. My guess is that you may have a bad record for "The K". You may have two records starting from the same position, one of which is incorrect. CSDS uses a binary search of the snapshot database, so if two records match the formation, it will choose the first one (with the highest priority and the lowest fuzziness rating) that it finds. Since the order of the actual records accessed by a binary search depends upon the number of records in the database, the program could match on a different snapshot record than was used when the sequence was written.

In any case, there are two validation functions for the snapshot database:

  1. Snapshot | Validate | Record Access: -- (this is the validation function that should help you resolve the problem) -- for each record within the specified range, the program sets up all possible starting positions specified in the record and then tries to execute the specified call specified. If the 'execute call' function does not match the record itself, a message is output to the output file. Hence this function basically searches for
    1. duplicate records, and
    2. superfluous records (which aren't exactly duplicates, but if they are deleted then the specified call would still be executed in the exact same manner).
    This function also finds occurrences when two records specify different ending formations for the same call from the same position, or when two records specify different roll attributes at the end of the call. I generally run this function on the snapshot database prior to major releases of CSDS. Feel free to run it, and experiment with the checkbox settings.
  2. Snapshot | Validate | Handle Lists: -- for each specified snapshot record, the program converts the handle list into a text string, then converts the text string back into a handle list. It then checks to see if the two handle lists match. Mismatches may indicate that there is a problem in the parse database, or the snapshot record may need to be edited to reflect the new handle list. A mismatch could also indicate that I need to rethink how the call is parsed.

ID: 254
  
  
  

full URL