Jump to content
SAU Community

Recommended Posts

see how bad the damage is from the scan. Determine If surgery is needed or not.

2-3 physio sessions a week to start with, stretches once 'healed' and then back into movements like running.

Start back into squats etc. once I get the ok. See how it goes

Depressing really, I feel I was makin good progress

Edited by jangles

Thats his heavy stuff done till States. He should total 650kg. This time last year I was lying in ICU so Max couldnt compete as he ran the show, he was at around 550kg. Before Nats he got injured, he was aiming for 600kg. At Worlds he got 650kg.

This year he is starting 100kg up. He plans to total around 725kg this year. The Junior WR is 690kgin the 90kg class.

At Worlds he weighed 86kg in the 90kg class, didnt have to make weight, in fact he's never had to make weight, lifting too light. 3 days before weigh in he was 84kg, he could easily have lifted in the 82.5kg, but he doesnt change plans midstream. He is currently 89.2kg in the morning.

By Nats he will have to make a decision as I reckon he might be 93-95kg, cut or lift in the hundreds, he's not fond of cutting, but he has definite plans and goals

he's very patient and focused... I'd back him to be over 700kg this year for sure

I trained yesterday at PCYC and had absolutely nothing... probably pushed myself a bit too hard, the stuffy nose and high temp came back last night... stupid cold has completely zapped me... still plenty of time to fully recover before states though... hopefully I can do some more quality heavy stuff this week, I'd like at least another sessions practice in the knee wraps

no excuses, I'll be ready come comp time and nothing bar a freak natural disaster is stopping me from a 200+kg squat

then 600+ at Nats..................

He weighed 77kg at the ProRawQualifier, benched 150kg

Today he weighed 83kg, benched 157.5kg

A few weeks ago he benched 80kg x 24, bodyweight

He actually filmed it for this website, I told him I wouldnt post it up, so he deleted it

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Latest Posts

    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...