theCrag / website

theCrag.com: Add your voice and help guide the development of the world's largest collaborative rock climbing & bouldering platform
https://www.thecrag.com/
109 stars 8 forks source link

Seasonality #1276

Closed howc37 closed 10 years ago

howc37 commented 10 years ago

Maybe it's caused by the last update, or I'm not patient enough.... I think the seasonality-graph doesn't update anymore.

I've been climbing in Sarmingstein (Sektor1) last Sunday, 6 days ago. http://www.thecrag.com/climbing/austria/area/339087708 http://www.thecrag.com/climbing/austria/area/339659868

October still says zero climbs.

scd commented 10 years ago

I had a quick look and there could be a problem here. I need to do a bit more investigation. Thanks for pointing it out.

howc37 commented 10 years ago

HI... it looks like it works for newer ascents? Here we have some November-Ascents showing up in the seasonality. http://www.thecrag.com/climbing/austria/area/331003320

For Sarmingstein http://www.thecrag.com/climbing/austria/area/339087708 nothing has changed.

scd commented 10 years ago

I have just done a code audit, and there is still nothing obvious. There is probably something really subtle going on which will take significant investigation. I just don't have time to look deeper into this at the moment given my other priorities.

howc37 commented 10 years ago

Update: http://www.thecrag.com/climbing/austria/area/339087708 (sector, climbs from October show up) http://www.thecrag.com/climbing/austria/area/339659868 (parent-crag, climbs from October don't show up)

scd commented 10 years ago

I redid a stats baseline for the area and it is fixed now.

The problem was that only one of the ascents from Oct in Sektor 1 was being counted. This one ascent was in the parent level so it was swamped by 22 ascents in Sep.

Doing a baseline meant the correct number was put into Sektor 1 and that was propagated up correctly.

I am guessing the root cause of this is that the statistics 'delta' mode is missing a hook when people change ascent dates. In otherwords ascents are entered with one date, but then later corrected. The statistics package is missing the trigger to correct the dates in the statics which remain wrong until a new baseline is done.

@howc37 could this be a possible scenario for the ascents you added?

howc37 commented 10 years ago

Hi Well, I did most of the ascents with my mobile phone. the date is automatically set in the app, so I guess, I've entered it. (But I can't remember if I did it on the correct day) it could have been... I'll keep an eye on it, next time.

howc37 commented 9 years ago

Just encountered last week: http://www.thecrag.com/climbing/austria/ewige-wand

The seasonality didn't update, when I logged the ascent on my mobile deice. Maybe you can have another look into this?

thx HowC

brendanheywood commented 9 years ago

I just had a look at this and have a few thoughts:

http://www.thecrag.com/climbing/austria/ewige-wand

1) in the feed there is only 1 ascent, under the stat summary there is 2 ascents. In the log book there is only 1 ascent. I just did some raw DB poking around and the stats, and the seasonality chart is showing private ticks while the atom feed and the logbook page are not so this is one bug source

2) The last updated date is 2 days after the tick was added, so that adds weird to the missing hook @scd mentioned above

howc37 commented 9 years ago

The last update was only for editing the text. (Done in the website)