[Az-Geocaching] Another Stats Problem?
Bill Tomlinson
listserv@azgeocaching.com
Tue, 24 Jun 2003 12:45:36 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_00BA_01C33A4E.82623480
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
So, after the stats were un-doubled (I kinda liked having all those =
finds),
I went in to see where I really stand. It was showing I had 9 out of =
state
finds which didn't seem right unless we have another cacher changing =
caches
mid-stream and messing up the counts. I grabbed all of my Arizona Finds
from AZGeocaching.com to track down the issue. Turns out only one of =
those
9 was for a members-only cache and one was for a locationless. The =
other 7
were regular Arizona caches. The only commonality I found was that they =
are
Archived, although I have other Archived finds that still count as AZ =
finds.
Perhaps it has to do with when they were archived. I didn't look any
further.
=20
Even stranger, I went back an hour later to see where I will stand when =
the
problem is fixed and it now shows 11 out of state finds. =20
=20
I have the details if it helps debug.
=20
CacheLess
------=_NextPart_000_00BA_01C33A4E.82623480
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D698413519-24062003><FONT face=3DArial size=3D2>So, =
after the stats=20
were un-doubled (I kinda liked having all those finds), I went in to see =
where I=20
really stand. It was showing I had 9 out of state finds which =
didn't seem=20
right unless we have another cacher changing caches mid-stream and =
messing up=20
the counts. I grabbed all of my Arizona Finds from =
AZGeocaching.com to=20
track down the issue. Turns out only one of those 9 was for a =
members-only=20
cache and one was for a locationless. The other 7 were regular =
Arizona=20
caches. The only commonality I found was that they are Archived, =
although=20
I have other Archived finds that still count as AZ finds. Perhaps =
it has=20
to do with when they were archived. I didn't look any=20
further.</FONT></SPAN></DIV>
<DIV><SPAN class=3D698413519-24062003><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D698413519-24062003><FONT face=3DArial size=3D2>Even =
stranger, I=20
went back an hour later to see where I will stand when the problem is =
fixed=20
and it now shows 11 out of state finds. </FONT></SPAN></DIV>
<DIV><SPAN class=3D698413519-24062003><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D698413519-24062003><FONT face=3DArial size=3D2>I have =
the details=20
if it helps debug.</FONT></SPAN></DIV>
<DIV><SPAN class=3D698413519-24062003><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D698413519-24062003><FONT face=3DArial=20
size=3D2>CacheLess</FONT></SPAN></DIV></BODY></HTML>
------=_NextPart_000_00BA_01C33A4E.82623480--