stephenbrooks.orgForumMuon1Bug ReportsCorrupt samples
Username: Password:
Search site:
Subscribe to thread via RSS
2004-06-06 02:49:12

I've seen this every now and then in both Phase and Chicane sample files.  Just disconnecting somewhere in the middle and starting a new value set without linefeed.  The a.m. dataset is the current leading one in the Phase-file as of 9:00 am

I'll start a single test now to see what the client does with it on its own.
2004-06-06 02:58:36
No matter what I do, the client ignores that result and starts randoms.  You can cut off the beginning string until the next"gen=x" then it will be recognized.
2004-06-06 07:06:35
Now I see what you mean, Herb.


That is an odd one.  I removed the junk #gen=4;#runs=5; and added a normal value in its place.  After that, it started to run, so apparently that was the only problem. 
It does look like an unusually high score for those parameters.  Interesting!
2004-06-10 10:41:40
We have again one of this kind
1.356358 (2233.3 Mpts) [v4.41b] <PhaseRotB>

Just cut away the beginning of the entry until the "gen=" starts
The values after that are fine.
2004-06-10 10:46:13
Correction: it must read cut away including "gen=6;"
2004-06-10 10:53:09
Yet another one in the Chicane
1.057137 (2273.9 Mpts) [v4.41b] <ChicaneLinacB>

becomes corrupt very late in the string, same procedure as above.
2004-06-10 13:22:05
..........and another one. 
1.366069 (452.6 Mpts) [v4.41a] <PhaseRotB> #time=44410; by Pollock[Romulus2]

is badly corrupted in the sample file.  Several values are listed twiceand others are missing.
2004-06-10 14:29:45
Duh Frown that corruption shows a different pattern, I wasn't able to isolate the true values yet.

I think it's about time to investigate the sample files algorythm??
2004-06-10 14:40:16
That result may have caused the corruption in the phaserot sample. 
It was an experimental version which added quite a few paramaters.  I was concerned that the script would have an issue with the size of the result. 
It appears that at least a part of the result may be mixed in with another one. 

Hopefully that is not the cause.  The future results are much, much more complex and still growing.  If it can't handle this one, it
will really have problems in the future.
2004-06-12 02:01:43
Yet another one in Chicane

1.018770 (464.8 Mpts) [v4.41b] <ChicaneLinacB>

This one is truncated right in the middle somewhere, but can be restored.  Delete behind the runs value up to the second occurring of d10l
2004-06-13 21:41:49
1.418469 (2235.1 Mpts) can be restored by deleting from the beginning including to the first occurrence of gen=6;
2004-06-14 07:34:31
1.601778 (2487.3 Mpts) delete from the beginning inclusive "gen=1;"
2004-06-16 01:00:10
1.686303 (2451.1 Mpts) delete up to and inclusive "gen=2;"
2004-06-16 01:14:39
1.073696 (2347.2 Mpts) [v4.41b] <ChicaneLinacB> same rule
2004-06-16 05:13:52
1.572162 (2388.9 Mpts) [v4.41b] <PhaseRotB> same rule
2004-06-17 23:58:21
1.677706 (2441.5 Mpts) [v4.41a] <PhaseRotB> same rule
: contact : - - -
E-mail: sbstrudel
Yahoo: scrutney_mallard
Jabber: stephenbrooksstrudel
Twitter: stephenjbrooks

Site has had 15784400 accesses.