20 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPA/NJ Backcountry Drives!
Leading reported evidence
Check with the wife and penciled it in
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
But I'm good to go either date, I've already checked with the wife and penciled it in on the calenedar.
Leading evidence: 'Check with the wife and penciled it in' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check into it and will get back' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Let me know your thoughts about the re-run proposal (I'm thinking May 19th or 26th) and for the July 28th date for another route.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Well, we could run the same route in the opposite direction.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I should say, too, that running the same route would be fun for me, and for those that missed yesterday's event.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I have also been asked to consider re-running today's route for those that are up for a second take on the curvy roads we put together and for those that could not make it today due to prior commitments.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
20 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T091943Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
All,
The Spring Fling went so well today, that I've a feeling that this is something just begging to be repeated. I'm pretty sure that those that could not make it today would be up for more drives.
I have marked July 28th (29th rain date) into my calendar for a new route.
I have also been asked to consider re-running today's route for those that are up for a second take on the curvy roads we put together and for those that could not make it today due to prior commitments.
Sooooo.... I'm open for comment. Let me know your thoughts about the re-run proposal (I'm thinking May 19th or 26th) and for the July 28th date for another route.
I'm open to assitance on this, as coming up with new routes takes time. If the demands is there, then we'll make it happen.
The 26th would most likely work for me, but that is the Memorial Day weekend, and I know a lot of people have plans for that. But I'm good to go either date, I've already checked with the wife and penciled it in on the calenedar. So if we want to vote on a date then start another official thread to get this ball rolling that would be great!! I would love to see that 356 again.
two considerations, post it on ppbb.com for the boxster buddies and one or two "pit" stops for us older guys and the girls. it was great, hope to see you in may or july.
I should say, too, that running the same route would be fun for me, and for those that missed yesterday's event.
I'd also look forward to a new route if that's your pleasure and the group concensus, perhaps using Jay's covered bridge tour.....either way, I'm in!
Well, we could run the same route in the opposite direction. I already have that prepared and that would give some different hill climbs.
I now have Jay's bridge tour and could work with that a little to come up with a new route.
Same route in reverse sounds great to me. Great selection of twisties, hills, and open stretches. All very scenic too. I'll gladly participate again if calendar permits.
...okay, I think that May might be a problem. I remembered that we have family in town on the weekend of the 19th, so that's out and we have a significant PCA conflct on the 26th, so May might now happen. I'm checking into it and will get back to people.
i wasn't going to say anything, but after telling you I was good for either day in May, my scheduling master (wife) informed me that neither day would work... so I'm not going to complain if we have to delay until June.
I know that feeling. It's pretty bad that May is as hectic as it is... one of the reasons why we had to run this weekend was that the next 6 weeks or so are so busy.
Oh well... give me more time to plan the next one without the stress of coming up with a new route at the same time.
New thread started!
Fling Spring : Saturday May 26th 2007
Lambertville, NJ
Say goodbye to Spring - hello to Summer with a speedy jaunt through the curvy and quiet back-roads of Eastern PA. Come equipped with a camera, your Porsche and ready for a spirited ride to show off the shine on your car.
Meeting point:
Lambertville Municipal Court
25 S Union St, Lambertville, NJ 08530
http://maps.google.com/maps?f=q&hl=...om=1&iwloc=addr
Arrive: 7:15 to 7:45am
Driver's Meeting 7:45am
Depart: 8am Sharp!
This is a source reference. Confirm exact model applicability in the original material.
