Update lotte_passages.py

lotte_passages.py

@@ -209,10 +209,10 @@ class NewDataset(datasets.GeneratorBasedBuilder):
 
                             if int(current_query["doc_id"]) == 119593 and len(data) == 268880: # Error rows for lifestyle
                                 print("Resolving error rows for lifestyle")
-                                error_rows = [{"doc_id": 119593, "author": "wabisabied", "text": "Can anybody point out what my problem with my guitar might be? Yes, it might be that the lighter gauge strings are sitting too deep in the nut slots. If the guitar was set up for heavier gauge strings, the slots will be wider than optimal for the new, lighter set, thus the strings will sit deeper and be too close to the frets. This can cause the buzzing, incorrect pitch and dead notes you are encountering. Reverting to heavier gauge strings might get you back on track, but you\u2019ll likely have to readjust saddles and truss rod, as well. In addition to the nut slot depth, the lower tension of lighter gauge strings will also reduce the relief, the slight concave bend, of the neck. This can also cause buzzing, incorrect pitch and dead notes. Since you tried adjusting relief with the truss rod to no better effect, I suspect the nut is a bigger impediment to a proper set up than the relief. Best solution at this point is to take it to a guitar tech, maybe the shop you bought from, and have it set up for the string gauges you prefer. As for the neck shifting and settling into bad alignment, it\u2019s hard to make any judgements without seeing it. If it truly is misaligned, then that is a structural problem and may warrant replacement under warranty. However a lot of new guitar players have problems with pushing the e string off the fret board, so it could just be part of the learning curve for you. Bottom line, I\u2019d take it to a tech and get it sorted out by an expert. However if you\u2019re still inclined to work it out yourself, Fender provides guidance for set ups here: How do I set up my Stratocaster guitar properly?"}
-                                              {"doc_id": 119594, "author": "Edward", "text": "Those look like chord symbols for the backing track. The book probably says this the first time that notation is used."}
-                                              {"doc_id": 119595, "author": "musicamante", "text": "Instead of focusing on the second bar, take a look at the first one. While the first note is a D, as the chord is, the second is clearly not an A, but its a C#. When you have [capitalized] letters on top of your staff, they most probably indicate the tonic (or the root) of the chord that is going to be played, not the specific note, otherwise the note to be played by the bass will be what is followed by the slash (if it exists), unless explicitly written in the instrument notation. In your case the bass line is written, but if its not and you see something like A/C# it means that the bass should theoretically play the C# note, even when the actual chord is A [major]: a more correct chord writing of the above would have A/C# written in the second half of the first measure. In this specific case, the text-written note does not indicate the root note of the chord (so it should be [A]), but the basic chord itself: C# is the third of A [major]. Do consider that it is possible that a note of the bass line can be a note that is not part of the overlying harmony: you can have a natural C in the bass, even if the harmony requires a C# (and even a B\u266d, which is not always the same thing)."}
-                                              {"doc_id": 119596, "author": "Aaron", "text": "According to the charts at https://norlanbewley.com/bewleymusic/trombone-slide-position-chart/ and https://olemiss.edu/lowbrass/studio/fingeringcharts/tenorandbasstromboneposition.pdf... note Norlan Bewliey position(s) Ole Miss position(s) C 1, 3, 5 1, 3 C#/Db 2, 4, 5 2, 5 D 1, 3, 4 1, short 3, 4 D#/Eb 3, 2 short 2, 3 E 2 2 F 1 1 F#/Gb 3 short 3 G 2 short 2 G#/Ab 3 3 A 2 2 A#/Bb 1 1, 3 B 2 C 1, 3 C#/Db 2 D 1, short 3 D#/Eb short 2, 3 E 2 F 1"}
+                                error_rows = [{"doc_id": 119593, "author": "wabisabied", "text": "Can anybody point out what my problem with my guitar might be? Yes, it might be that the lighter gauge strings are sitting too deep in the nut slots. If the guitar was set up for heavier gauge strings, the slots will be wider than optimal for the new, lighter set, thus the strings will sit deeper and be too close to the frets. This can cause the buzzing, incorrect pitch and dead notes you are encountering. Reverting to heavier gauge strings might get you back on track, but you\u2019ll likely have to readjust saddles and truss rod, as well. In addition to the nut slot depth, the lower tension of lighter gauge strings will also reduce the relief, the slight concave bend, of the neck. This can also cause buzzing, incorrect pitch and dead notes. Since you tried adjusting relief with the truss rod to no better effect, I suspect the nut is a bigger impediment to a proper set up than the relief. Best solution at this point is to take it to a guitar tech, maybe the shop you bought from, and have it set up for the string gauges you prefer. As for the neck shifting and settling into bad alignment, it\u2019s hard to make any judgements without seeing it. If it truly is misaligned, then that is a structural problem and may warrant replacement under warranty. However a lot of new guitar players have problems with pushing the e string off the fret board, so it could just be part of the learning curve for you. Bottom line, I\u2019d take it to a tech and get it sorted out by an expert. However if you\u2019re still inclined to work it out yourself, Fender provides guidance for set ups here: How do I set up my Stratocaster guitar properly?"},
+                                              {"doc_id": 119594, "author": "Edward", "text": "Those look like chord symbols for the backing track. The book probably says this the first time that notation is used."},
+                                              {"doc_id": 119595, "author": "musicamante", "text": "Instead of focusing on the second bar, take a look at the first one. While the first note is a D, as the chord is, the second is clearly not an A, but its a C#. When you have [capitalized] letters on top of your staff, they most probably indicate the tonic (or the root) of the chord that is going to be played, not the specific note, otherwise the note to be played by the bass will be what is followed by the slash (if it exists), unless explicitly written in the instrument notation. In your case the bass line is written, but if its not and you see something like A/C# it means that the bass should theoretically play the C# note, even when the actual chord is A [major]: a more correct chord writing of the above would have A/C# written in the second half of the first measure. In this specific case, the text-written note does not indicate the root note of the chord (so it should be [A]), but the basic chord itself: C# is the third of A [major]. Do consider that it is possible that a note of the bass line can be a note that is not part of the overlying harmony: you can have a natural C in the bass, even if the harmony requires a C# (and even a B\u266d, which is not always the same thing)."},
+                                              {"doc_id": 119596, "author": "Aaron", "text": "According to the charts at https://norlanbewley.com/bewleymusic/trombone-slide-position-chart/ and https://olemiss.edu/lowbrass/studio/fingeringcharts/tenorandbasstromboneposition.pdf... note Norlan Bewliey position(s) Ole Miss position(s) C 1, 3, 5 1, 3 C#/Db 2, 4, 5 2, 5 D 1, 3, 4 1, short 3, 4 D#/Eb 3, 2 short 2, 3 E 2 2 F 1 1 F#/Gb 3 short 3 G 2 short 2 G#/Ab 3 3 A 2 2 A#/Bb 1 1, 3 B 2 C 1, 3 C#/Db 2 D 1, short 3 D#/Eb short 2, 3 E 2 F 1"},
                                               {"doc_id": 119597, "author": "musicamante", "text": "This question could have tons of answers, but most of them would be based on psychoacustics (even if they are not aware about that). Its mostly about size and perception. Think about listening to two sounds. What would you listen better (or, what you could better differentiate)? listening to both sounds coming from the same source listening to those sounds coming from different positions The simple answer is clearly the second, but that depends on a sum of factors. Different sounds (most importantly, similar sounds, including two voices, no matter how different they could be) often have common frequencies that often create ghost notes in our heads (look up for Auditory illusions). Having [at least] two different sounds coming from two distinct sources (our two ears), makes us easier to make a better distinction between them and allows us to better create the correlation between those sounds. Its not that different from what the binocular vision allows us (I know, its not the same, but its just for the example): imagine seeing an apple on the proverbial table. When you see the same image from your left eye and from your right eye, youd have no depth perception. Yes, its almost the same image, but thats just it, a perception of an apple on a table. Having different (and, obviously, correlatable) images from both eyes gives you a hugely different perception of what youre seeing. You can see the size of the apple, related to that of the table; you can picture the size of the apple; if you were to touch the apple, you would certainly be able to on the first attempt. The same happens in the panning of similar (but differently-voiced) vocals. It gives them space. And a three-dimensional object is usually much more interesting than a bidimensional one. Having two similar sounds (as in doubled vocals, which share lots of common frequencies), creates more space, and makes it much more interesting. It is not the same as having a guitar on the left and a drum on the right, as theres much less correlation between them. Having doubled vocals on different positions makes them bigger, which, on our minds, also makes them more important."}]
                                 for row in error_rows:
                                     yield row['doc_id'] + 1, {
@@ -250,3 +250,5 @@ class NewDataset(datasets.GeneratorBasedBuilder):
                             }
 
 
+
+