Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add English pacenotes for 'Scotland - Newhouse Bridge' #8

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

taoceanz
Copy link

@taoceanz taoceanz commented Jun 7, 2021

Added pacenotes according to Jemba system.
Abbreviation inspiration taken from the Jemba website:
https://www.jemba.se/notesUSA.htm

Formatting inspiration taken from the Targa NZ website
https://targa.nz/wp-content/uploads/2020/02/Rally-Sprint-Safety-Notes.pdf

I've added periods between the corner grade+direction and the duration to avoid potential confusion e.g. 5Llg becomes 5L.lg with a period.
Adding the duration before the grade+corner (E.g. lg5L) also avoids the confusion, but doesn't align with how the co-driver makes the majority of calls.

@maxbechtold
Copy link
Owner

Thanks for the contribution @taoceanz!
Do you have a recorded run for verification? I'm not sure when I get to do this stage on my own.

Since this is the first contribution, I'm pondering about the system. Afaik Jemba is used in several countries, but then there are other notation systems as well. The one I used for the existing stages looks a bit simpler/concise, so I wonder if we could discuss adaptations to your Newhouse Bridge notes, e.g. [up] for "uphill" or rocks-in for (rocks inside).
Is "to" the same as "into"?

@taoceanz
Copy link
Author

My pleasure, @maxbechtold. I'm new to DiRT Rally 2.0 and not great on the game so don't have a verification run. I have an audio recording which I used to make the notes. One of my main reasons to contribute is to use German Route Notes while playing because I'm learning German. My idea is to add English Route Notes cross reference to understand the German Route Notes.

Preword to the stuff below. At the end of the day, I'm contributing to your repo, so anything you say goes. I'm keen to help build your repo because the Route Note stuff around DiRT Rally is pretty dire. Anyway though these are my thoughts.

Overall I think it's better to stay as close to an official system as possible. There's less misunderstandings and a solid standard to build. In saying that, even for Jemba, there's a couple variations of it. Also using an existing system makes it easier for existing co-drivers or aspiring co-drivers to use the notes. More common understanding.
The DiRT Rally 2.0 Route Notes seem to follow the 'Six Fastest' notation described at this link. Very similar to the 'McRae In Gear' notation I've seen some articles mention DR2.0 follows.
https://www.rallynews.net/pattersonpacenotes/systemtypes.asp

With 'into', I've not found any notes that use 'to' instead of 'into'. I think it's to avoid confusion with the number 2 e.g. 2R to 2L>1 to late 3<2 to SqL. In saying that, I'm not opposed to using 'to' instead of 'into', just think using 'to' could be more confusing.

With 'uphill', from a drivers perspective, I'd specifically want to hear the road is going up hill or down hill. It can drastically change an approach. Having 'uphill' in the notes leaves less resistence for the co-driver to say that exact thing. Having 'up' is more ambiguous and puts more cognitive load on the co-driver to see the note and translate to the most accurate words to use for the call. If you're set on using 'up' I'm happy to change it.

With 'rocks inside', rather than 'thing-in/thing-out' or 'thing in/thing out', I propose using pattern 'thingIn/thingO' e.g.

  • keepIn and keepO
  • slowIn and slowO
  • ditchIn and ditchO
  • rockIn and rockO

If you're interested, I'd been keen to make an official glossory of all possible calls, there descriptions, and the notation to be used. I know you've already got a bunch of this in your README, though would be good to get all possible calls in a dedicated file for each of the games because they seem to use different systems. Also there are some calls not mentioned in the README.

Anywho, what are your thoughts on all of this? All good if your think it's all shit! :D

@maxbechtold
Copy link
Owner

Thanks for the context, do you have any real-life experience by chance? How funny you use the German notes, as this is my mother tongue and I never bothered to change from the English pace notes.

I found this recording, it's not a totally clean run, but will probably work to verify the notes: https://www.youtube.com/watch?v=zW7uQY0cNLM

You're right, it's the Six Fastest notation, and I shall include a link to the RallyNews explanation in the README. But this is only corners, the rest seems to be up to the co-driver themselves, no?
We can discuss adaptations of the schema in the README, but in the end all pace notes should adhere to the schema.

Going into the suggested changes:

  • I agree reading "to" can be mistaken as "2" and the notes should then use "into".
    The current system doesn't even bother with this detail, as I may have said I tried to keep it simple. But if you like, extend your PR and add this in the section "Note succession"
  • I'm fine with using uphill and downhill verbatim, but then please adapt the existing notes (it's been used in a few places already). Also, please add the [braces] as in the system
  • the README is the glossary for the purpose of this repository. They might be calls missing, particular for the later recordings of Scottish tracks, but how much is it actually? I think it's fine if the system is extended little by little, and you're welcome to do so
  • with respect to splitting it for DR1 and DR2, I think they are rather similar, and DR2 mostly adds a few things here and there. Perhaps the corner notation is a bit too concise, maybe this section could be improved in the README
  • thingIn/thingOut would work for me, let's not be mean with those 2 letters in out ;) Again, please adapt the README and existing notes.

Again thanks for the input, I shall try to respond timely, but have little time to spare in the next weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants