Mostly yellow and red. I will have ridden 17 days since March 1 after tomorrow, then 4 days off for travel, and back to the cold wet/snowy north.
Sounds like you have suddenly stepped up the volume of work, so I would expect a lot of reds and yellows - so operating as it should.
I’m assuming this means you training will drop when you get back.
As Tr say, if you know the volume is higher and you know there is a planned reduction or break, then working through the reds and yellows is okay.
The feature is there to help promote consistent training and progressive overload which are known to make you faster.
Curious to hear thoughts on a behavior (I think) I’ve observed which is a bias towards suggesting yellow days on run/swim workouts but not on bike workouts.
I’ve had a few yellow days in the last couple weeks that fell on days with a run/swim or both. (I’m on LV 70.3). On almost all of those days I’ve either accepted the annotations (and often just did the original workout 
) or declined annotation. I would expect the following day (generally a bike workout) to then be yellow but often it’s back to green!
For example the last 3 days
Out of curiosity, are you entering TSS for your swim workouts?
Good call. I’m not - I had assumed swim had an assumed TSS associated with it. Looks like I need to start adding that!
I’m not sure it will change what you’re seeing. I was thinking maybe it assumes swims are 0 TSS (which is what they have by default) and then it gets surprised if they aren’t.
This is possible in run workouts too, the TSS in Plan Builder often doesn’t correspond to the workout at all. That’s been an issue as long as I remember using TR.
Red light green light only uses your activities that are on the calendar. Obviously activities on the bike count if you have power data or heart rate data. Guessing running data is included since tr does running. What other activities are factored in? I do lots of hikes with my Garmin watch so that data is there but not sure it impacts this.
No other data is used in this calculation, right? Obviously tr can only factor in data it knows about. It would be possible for tr to use the 24/7 data my Garmin Fenix 7 records about me. (Hours slept, resting heart rate, night time hrv, stress during the day, etc) But guessing tr doesn’t use this info. Seems like this data would be very important to know if my recovery is the same as normal, if it’s a more relaxing week then normal, or if it’s a very stressful week with less sleep. Any plan for doing this?
Iirc someone at TR mentioned in the RLGL early access thread that it considered the actual work done in the run vs what TR had originally estimated.
Swims don’t have that same data (TSS is set to 0 and swims aren’t imported) so I think it makes sense for me to try to manually enter the TSS
If you don’t like TSS then imagine the word just says “load” or “difficulty”. It doesn’t change anything whatsoever about the argument.
I’m not sure what a 0 TSS run is. You sit in the couch for an hour and look at your shoes? 
I repeat, because apparently the first time it wasn’t clear enough: if you don’t like TSS (and you clearly don’t), then please read “load” or “intensity” where we wrote TSS. Because it does use that, per the description. Also, notice this in the FAQ:
"Do my outside activities need power data to be considered by RLGL?
Nope! Activities that only have Heart Rate data will count if you use TrainerRoad’s Heart Rate TSS Estimation."
Oh no, the TSS word! Interesting that you need to compute it so TR can then…throw it away, according to you? Anyway…
The workouts have a TSS assigned. Just look in your calendar.
(it’s often wrong when you compare the RPE and duration in the workout, but it’s there)
If you’re saying that runs where TR doesn’t have any heart rate data can cause yellow days, this would mean their FAQ is incorrect (see previous post) or they were caused by something else, I think?
Just confirming same here. Wearing an HRM but no power and runs come in with 0 TSS. I then used the RPE drop down to get TSS estimates entered.
The runs have a predicted TSS assigned which is used in the plan overviews (and can be seen in the Calendar). The actual TSS after the workout needs manual entry, and Hr TSS estimation never works for me there.
Given the FAQ statement that outside workouts need at least a computed TSS to be accounted for, it seems reasonable it must be an important part of the calculation.
That’s why it’s a bit weird for @Bbt67 to see yellow days being caused by days where you don’t enter the TSS, unless it’s using the TSS from the plan.
And swim days DON’T have an estimated TSS in the plan. But you can enter it, and perhaps this surprises the algo. That was the original point I was trying to make.
The description of the workout has something like “run 50 minutes at RPE7”. You can calculate the TSS from this - if the workout is correctly executed the resulting (Hr or Pwr or …) TSS should be close.
But in some workouts the TSS that is in the Calendar looks pretty far off from what executing the workout would give (I think this is just a bug - it’s been this way for years).
Got it! So if you’d do a 2h walk in the city…it may just give you a red day? 
If those runs without any data still influence RLGL I’m not surprised multisport people are seeing strange things.
Walking my dogs and using my watch to measure the distance turned a yellow day to red when I finally uploaded it from garmin connect
Well that was an interesting to and fro.
A more important factor is past training, whether it’s run or bike (swim is being worked on in the background). So if you do a hard run (or a long walk) and it’s a similar load/frequency over time you’ll be good. If you haven’t run in six weeks a nail a tempo run, you should expect a red day tomorrow. Same as for biking.
It’s been fun to check it thus far. The internal happy maker in me would love to see a hint of green for go on good days. That part of my brain wants the “reward”.
Curious as to how the TSS plays into each ride. If you look at my past two weeks, the X ride was by far the most taxing, It was 4 hours straight (One 2 min break to fill bottles) of constant pedaling with 0.7 IF.
If you look at the previous Monday (red tick), it was an hour longer at 0.67 IF. But on that ride there were a couple of 30+ min climbs followed by long descents. Between that and two stops at around 5 min each there was a lot more down time.
My point is if you do the same effort but on one ride you take a bunch of 5-10 min breaks and the other you take none, you would assume one would be rated significantly harder than the other.
For the record, the second red tick on the right (Ojai) felt by far the easiest. Basically it was a 2.5 hour climb followed by a one hour (pedaling descent).
