Since the second half also dragged on, here's a continuation of the second half.
Since it's the previous article, I won't put a link.
The other day, on a day I had off,
I got an email from my mentor saying "my finger died" (sic).
A frame builder retirement crisis!!
Apparently, the tire won't come off the rim.
The customer apparently gave permission to worst-case scenario cut the tire with a knife and remove it,
but there's no way a tire won't come off, so just wait a bit
I'll head over there for some training anyway
and don't come home for about another hour.
So I went to the workshop in Kawachinagano.
When I saw the actual bike,
an IRC Aspite Pro latest model was on
a certain tubeless-ready (requires rim tape) aluminum rim.
The reason I specifically noted "latest model" is that
the current Aspite Pro is a rare tire that
supports hookless rims despite not being tubeless-compatible.
The sharp, angular bead section for hookless compatibility
had bitten hard into the rim's hook,
and when I pressed hard on the tire sidewall with both thumbs to release the bead lift,
the tire suddenly dropped toward the rim center—BAHOP—
and after that, though it was a bit stiff,
I was able to remove the tire using tire levers.
I said about this that what was needed was "technique,"
and even if I were a half-dead old man,
I could get this off.
But my mentor insists it was due to power,
pure muscle strength.
Well, I understand that sentiment.
If he admitted it was "technique," it would mean
acknowledging that in a certain field
there are aspects of technical skill, knowledge, and experience
where I as a newcomer fall short.
But if he just admits to raw muscle power,
it doesn't wound his pride.
One more thing. In the corner of the workshop
there was a Trencle, a titanium ultra-lightweight folding bike
that Panasonic used to make.
My mentor is a pioneer in customizing these.
It has the latest Dura-Ace crankset at the time, FC-7700, on it,
but for some reason only the right side is installed.
Apparently the left crank came off,
but the right crank's fixing bolt won't come loose.
Right, lend me tools—with a torque extension bar
Hold the frame down I'm gonna apply some force—URRRRAAAA!
When I applied force, it made a nice CACKLING sound
and initial breakloose was achieved, so
after that the bolt turned easily.
This is not technique. This is power.
Right before heading to my mentor's place,
there's a road that dips like a mortar—"downhill→bottom→uphill"—
and on the return side, if I add pedaling strokes to the coasting momentum from the downhill,
I can reach about 50 km/h at the bottom of the depression, then struggle upward
and escape the depression before the coasting momentum runs out
and I slow to the normal climbing speed for that grade.
But the side going there is steeper,
and I use up the downhill momentum and
slow to the normal climbing speed for that grade.
To make matters worse,
starting in 2013, a bypass tunnel (Akamine Tunnel) from the Gaikansajo Line (National Route 170)
opened at the bottom of the depression, creating
an intersection and traffic signal.
Now I hit red lights with high probability.
In other words, I now have to climb
a steep section that would normally use 50 km/h of coasting momentum
from a complete stop.
There is actually a detour route for this road,
but it's a bit complicated, so I don't use it.
↑The actual intersection.
The point where I've climbed to where I can see from here,
to where I can see from here,
the traffic signal intersection visible from this point
is the top of the hill,
and it's also where I turn right to go to my mentor's workshop.
Still just barely can't see the top intersection.
And right about then, Karoo's climb recognition
appeared with a ridiculously loud beep,
and the Climb 1 notification folder
rose up from the bottom to cover half the screen.
Just like the right/left turn instructions on route navigation,
the folder rises up at 150 meters remaining,
and with 150 m as the full screen width,
the color darkens from left to right.
So the state shown in the screen above means
Climb 1 starts about 90 meters ahead,
with distance 1.2 km and elevation gain 37 m.
The reason the cycle computer's trip distance shows 0.2 km
is because I started recording from the bottom intersection.
I rode a bit,
and the remaining distance is still 1.2 km
but the elevation gain decreased by 1 m.
The 11.6% grade shown at the beginning of the elevation graph
isn't false—it matches my physical sensation.
If I could clear this section using downhill momentum,
it would be a bit easier.
Looking at the Climb 1 route on the map.
The blue line from the triangle flag to the checkered flag
is the Climb 1 route.
When I go to my mentor's place,
I turn right at the red arrow,
so I don't actually complete Climb 1.
I've climbed the steepest section.
About where I can barely see the traffic signal at the top intersection.
Out of the 1.2 km distance, I've covered 0.2 km
and consumed 16 m out of 37 m elevation gain.
The 1 m minimum unit for elevation aside,
the 0.1 km increments for distance are a bit coarse
(the difference between the next 0.1 km switching being 10 m away or 60 m away is significant),
but doing simple math, I've consumed
43% of the elevation gain in the first 16% of the distance.
The top signal is coming into view.
In 0.1 km, I've only climbed 1 m.
And for some reason, right about here every time
Climb 1 silently just disappears,
not even showing "Complete"
—it becomes "as if it never happened."
I didn't make a U-turn or turn the bike at an angle or anything.
This is a phenomenon with 100% reproducibility so far.
Either way, I'm going to turn right at the next signal,
and based on the Rokko mountain example,
it should record up to where it was interrupted
as Climb 1.
But it gets erased as if it never happened before then.
In the first part of the article,
when I did route navigation from my house to Fukkitouge Pass,
Climbs 1-4 appeared on the navigation course,
but the first Climbs 1 and 2 became "as if they never happened"
when I ignored the navigation and entered a road
I definitely won't travel again.
The original Climbs 3 and 4 got bumped up to Climbs 1 and 2.
That Climb 1 includes a motorway,
so I couldn't follow the navigation exactly.
I entered the old road running alongside it, and after riding for a while,
Climb 1 also became "as if it never happened,"
and the original Climb 4 eventually got bumped up to the final Climb 1.
These three climbs that "never happened"
weren't actually ridden on that route.
But in this hill case, Climb 1 shows
progress in distance, elevation, and elevation graph
as I'm actively consuming the Karoo climb recognition route,
yet it becomes "as if it never happened."
I thought, maybe climbs don't complete
if the distance ridden is too short even while consuming them?
But looking at the data from the second part article
where I left the Rokko golf course area and turned left at the Koujuji Bridge intersection
(going straight per route without climbing Rokko)
and entered the Washinji temple route, at that exact moment
Climb 2 completed,
and I had ridden 0.4 km.
In this hill case, my trip distance was 0.3 km.
Does "never happened" status occur for 0.3 km or less?
No, before that,
I was actually riding on the climb route
and didn't leave the route by U-turning or turning.
※I'll quote this later
At that moment, I remembered
a hill in front of Abeno Harukas in Tennoji
that for some reason Karoo recognizes as a climb.
Clearly if I ride on the car lane, Climb 1 appears,
but if I ride on the sidewalk or right at the sidewalk edge of the car lane,
Climb 1 doesn't appear.
I'm riding to the right of the white dotted line in the car lane on this hill too,
but maybe I need to get closer to the center line for
"Karoo to GPS-wise judge that I'm riding on the climb route"
to stay within range, I thought.
So I went back to the bottom of the depression again,
and from just before the "point where Climb 1 becomes erased,"
I rode right along the orange center line.
But there's an awful lot of car traffic on this road.
Maybe it's the rush hour when people are heading home from work,
or maybe the bypass increased traffic,
but cars that launched when the light turned green at the bottom
catch up to me just right
before I finish climbing to the signal.
Obviously once I see a car coming up behind me,
I can't ride near the center line,
and this image is from when I'd moved left to about the white line
so as not to inconvenience the cars,
and sure enough, Climb 1 had become "as if it never happened,"
so I stopped to capture it.
The timing made it impossible to tell whether
"it had become erased by the time I reached this point anyway"
or
"it was judged that I'd left the climb route by moving left."
So I went back to the bottom intersection again,
did a fresh Karoo recording,
and tried to pass through the "point where it becomes erased"
near the center line,
but again got caught up to by a car.
I did this about 4 times,
but each time I had car interference (← from my perspective;
the cars did absolutely nothing wrong, just to be clear),
and I felt like I was stacking stones in Sai no Kawara,
and while my legs got tired, my mind broke even more,
so I wasn't able to get results on whether
"Climb 1 would continue if I passed through the top intersection near the center line."
As far as I know, the only hill
showing the behavior of an active climb mysteriously becoming "as if it never happened"
is this one, and reproducibility is 100%.
Of the 4 times on Sai no Kawara climb,
2 times left recorded data.
↑I rode the same section,
but the elevation graphs are slightly different,
so this isn't referencing information from the map—
these are measured values from the barometer.
This much was already clear from when I manually stopped recording
near Seko River's start,
and the elevation record became a vertical cliff from the barometric changes before and after.
I stopped recording at the point where Climb 1 disappeared,
but in both cases, I'd apparently
left the road and plunged into a field.
※From earlier quote:
I was actually riding on the climb route
and didn't leave the route by U-turning or turning.
↑According to the reconciliation between
Karoo's GPS information and map information,
it appeared I had left the route.
So if I get the chance in the future,
I'd like to try riding on the opposing lane's sidewalk
rather than right along the center line of my lane.
The sidewalk has almost no pedestrians,
and even if cars come, it doesn't matter.
Looking closely at the Rokko mountain U-turn incident where Climb 1 completed,
the blue climb recognition route broke precisely
where it left the road.
So maybe if I'd U-turned without leaving the road,
the climb wouldn't have cut short and completed.
Since it's the previous article, I won't put a link.
The other day, on a day I had off,
I got an email from my mentor saying "my finger died" (sic).
A frame builder retirement crisis!!
Apparently, the tire won't come off the rim.
The customer apparently gave permission to worst-case scenario cut the tire with a knife and remove it,
but there's no way a tire won't come off, so just wait a bit
I'll head over there for some training anyway
and don't come home for about another hour.
So I went to the workshop in Kawachinagano.
When I saw the actual bike,
an IRC Aspite Pro latest model was on
a certain tubeless-ready (requires rim tape) aluminum rim.
The reason I specifically noted "latest model" is that
the current Aspite Pro is a rare tire that
supports hookless rims despite not being tubeless-compatible.
The sharp, angular bead section for hookless compatibility
had bitten hard into the rim's hook,
and when I pressed hard on the tire sidewall with both thumbs to release the bead lift,
the tire suddenly dropped toward the rim center—BAHOP—
and after that, though it was a bit stiff,
I was able to remove the tire using tire levers.
I said about this that what was needed was "technique,"
and even if I were a half-dead old man,
I could get this off.
But my mentor insists it was due to power,
pure muscle strength.
Well, I understand that sentiment.
If he admitted it was "technique," it would mean
acknowledging that in a certain field
there are aspects of technical skill, knowledge, and experience
where I as a newcomer fall short.
But if he just admits to raw muscle power,
it doesn't wound his pride.
One more thing. In the corner of the workshop
there was a Trencle, a titanium ultra-lightweight folding bike
that Panasonic used to make.
My mentor is a pioneer in customizing these.
It has the latest Dura-Ace crankset at the time, FC-7700, on it,
but for some reason only the right side is installed.
Apparently the left crank came off,
but the right crank's fixing bolt won't come loose.
Right, lend me tools—with a torque extension bar
Hold the frame down I'm gonna apply some force—URRRRAAAA!
When I applied force, it made a nice CACKLING sound
and initial breakloose was achieved, so
after that the bolt turned easily.
This is not technique. This is power.
Right before heading to my mentor's place,
there's a road that dips like a mortar—"downhill→bottom→uphill"—
and on the return side, if I add pedaling strokes to the coasting momentum from the downhill,
I can reach about 50 km/h at the bottom of the depression, then struggle upward
and escape the depression before the coasting momentum runs out
and I slow to the normal climbing speed for that grade.
But the side going there is steeper,
and I use up the downhill momentum and
slow to the normal climbing speed for that grade.
To make matters worse,
starting in 2013, a bypass tunnel (Akamine Tunnel) from the Gaikansajo Line (National Route 170)
opened at the bottom of the depression, creating
an intersection and traffic signal.
Now I hit red lights with high probability.
In other words, I now have to climb
a steep section that would normally use 50 km/h of coasting momentum
from a complete stop.
There is actually a detour route for this road,
but it's a bit complicated, so I don't use it.
↑The actual intersection.
The point where I've climbed to where I can see from here,
to where I can see from here,
the traffic signal intersection visible from this point
is the top of the hill,
and it's also where I turn right to go to my mentor's workshop.
Still just barely can't see the top intersection.
And right about then, Karoo's climb recognition
appeared with a ridiculously loud beep,
and the Climb 1 notification folder
rose up from the bottom to cover half the screen.
Just like the right/left turn instructions on route navigation,
the folder rises up at 150 meters remaining,
and with 150 m as the full screen width,
the color darkens from left to right.
So the state shown in the screen above means
Climb 1 starts about 90 meters ahead,
with distance 1.2 km and elevation gain 37 m.
The reason the cycle computer's trip distance shows 0.2 km
is because I started recording from the bottom intersection.
I rode a bit,
and the remaining distance is still 1.2 km
but the elevation gain decreased by 1 m.
The 11.6% grade shown at the beginning of the elevation graph
isn't false—it matches my physical sensation.
If I could clear this section using downhill momentum,
it would be a bit easier.
Looking at the Climb 1 route on the map.
The blue line from the triangle flag to the checkered flag
is the Climb 1 route.
When I go to my mentor's place,
I turn right at the red arrow,
so I don't actually complete Climb 1.
I've climbed the steepest section.
About where I can barely see the traffic signal at the top intersection.
Out of the 1.2 km distance, I've covered 0.2 km
and consumed 16 m out of 37 m elevation gain.
The 1 m minimum unit for elevation aside,
the 0.1 km increments for distance are a bit coarse
(the difference between the next 0.1 km switching being 10 m away or 60 m away is significant),
but doing simple math, I've consumed
43% of the elevation gain in the first 16% of the distance.
The top signal is coming into view.
In 0.1 km, I've only climbed 1 m.
And for some reason, right about here every time
Climb 1 silently just disappears,
not even showing "Complete"
—it becomes "as if it never happened."
I didn't make a U-turn or turn the bike at an angle or anything.
This is a phenomenon with 100% reproducibility so far.
Either way, I'm going to turn right at the next signal,
and based on the Rokko mountain example,
it should record up to where it was interrupted
as Climb 1.
But it gets erased as if it never happened before then.
In the first part of the article,
when I did route navigation from my house to Fukkitouge Pass,
Climbs 1-4 appeared on the navigation course,
but the first Climbs 1 and 2 became "as if they never happened"
when I ignored the navigation and entered a road
I definitely won't travel again.
The original Climbs 3 and 4 got bumped up to Climbs 1 and 2.
That Climb 1 includes a motorway,
so I couldn't follow the navigation exactly.
I entered the old road running alongside it, and after riding for a while,
Climb 1 also became "as if it never happened,"
and the original Climb 4 eventually got bumped up to the final Climb 1.
These three climbs that "never happened"
weren't actually ridden on that route.
But in this hill case, Climb 1 shows
progress in distance, elevation, and elevation graph
as I'm actively consuming the Karoo climb recognition route,
yet it becomes "as if it never happened."
I thought, maybe climbs don't complete
if the distance ridden is too short even while consuming them?
But looking at the data from the second part article
where I left the Rokko golf course area and turned left at the Koujuji Bridge intersection
(going straight per route without climbing Rokko)
and entered the Washinji temple route, at that exact moment
Climb 2 completed,
and I had ridden 0.4 km.
In this hill case, my trip distance was 0.3 km.
Does "never happened" status occur for 0.3 km or less?
No, before that,
I was actually riding on the climb route
and didn't leave the route by U-turning or turning.
※I'll quote this later
At that moment, I remembered
a hill in front of Abeno Harukas in Tennoji
that for some reason Karoo recognizes as a climb.
Clearly if I ride on the car lane, Climb 1 appears,
but if I ride on the sidewalk or right at the sidewalk edge of the car lane,
Climb 1 doesn't appear.
I'm riding to the right of the white dotted line in the car lane on this hill too,
but maybe I need to get closer to the center line for
"Karoo to GPS-wise judge that I'm riding on the climb route"
to stay within range, I thought.
So I went back to the bottom of the depression again,
and from just before the "point where Climb 1 becomes erased,"
I rode right along the orange center line.
But there's an awful lot of car traffic on this road.
Maybe it's the rush hour when people are heading home from work,
or maybe the bypass increased traffic,
but cars that launched when the light turned green at the bottom
catch up to me just right
before I finish climbing to the signal.
Obviously once I see a car coming up behind me,
I can't ride near the center line,
and this image is from when I'd moved left to about the white line
so as not to inconvenience the cars,
and sure enough, Climb 1 had become "as if it never happened,"
so I stopped to capture it.
The timing made it impossible to tell whether
"it had become erased by the time I reached this point anyway"
or
"it was judged that I'd left the climb route by moving left."
So I went back to the bottom intersection again,
did a fresh Karoo recording,
and tried to pass through the "point where it becomes erased"
near the center line,
but again got caught up to by a car.
I did this about 4 times,
but each time I had car interference (← from my perspective;
the cars did absolutely nothing wrong, just to be clear),
and I felt like I was stacking stones in Sai no Kawara,
and while my legs got tired, my mind broke even more,
so I wasn't able to get results on whether
"Climb 1 would continue if I passed through the top intersection near the center line."
As far as I know, the only hill
showing the behavior of an active climb mysteriously becoming "as if it never happened"
is this one, and reproducibility is 100%.
Of the 4 times on Sai no Kawara climb,
2 times left recorded data.
↑I rode the same section,
but the elevation graphs are slightly different,
so this isn't referencing information from the map—
these are measured values from the barometer.
This much was already clear from when I manually stopped recording
near Seko River's start,
and the elevation record became a vertical cliff from the barometric changes before and after.
I stopped recording at the point where Climb 1 disappeared,
but in both cases, I'd apparently
left the road and plunged into a field.
※From earlier quote:
I was actually riding on the climb route
and didn't leave the route by U-turning or turning.
↑According to the reconciliation between
Karoo's GPS information and map information,
it appeared I had left the route.
So if I get the chance in the future,
I'd like to try riding on the opposing lane's sidewalk
rather than right along the center line of my lane.
The sidewalk has almost no pedestrians,
and even if cars come, it doesn't matter.
Looking closely at the Rokko mountain U-turn incident where Climb 1 completed,
the blue climb recognition route broke precisely
where it left the road.
So maybe if I'd U-turned without leaving the road,
the climb wouldn't have cut short and completed.