Read the event before you arrive
Generated from
content/lms/getting-started-with-hpde/01-what-is-hpde/02-how-events-work.md; edit the source file, not this page.
Source path: content/lms/getting-started-with-hpde/01-what-is-hpde/02-how-events-work.md
Course: Getting Started with HPDE
Module: What is HPDE?
Estimated duration: 55 minutes
The skill in this lesson is not reading for trivia. It is reading an HPDE event packet the way you would read the track surface before turn-in: looking for the facts that will decide what you do next. Before you arrive, the event has already told you how the day is supposed to work. The schedule tells you when your run group is on track, when mandatory meetings happen, where inspections or classrooms take place, and how much track time you should expect. The rule packet tells you what the organizer considers acceptable conduct, what equipment is required, what local procedures are different at this track, and what will keep you from being allowed on track. The preparation guide tells you what must be handled before you leave home: tech inspection, helmet standard, car numbers, paperwork, water, clothing, and the basic homework that lets the first session become learning instead of confusion.
Intermediate drivers sometimes under-read event documents because they have already survived a few HPDE days. That is exactly when the habit matters more. Your first event teaches you that HPDE has flags, run groups, tech, instructors, and classroom. Your next events teach you that none of those details are identical from club to club, region to region, or facility to facility. A rule that was informal at one event may be mandatory at the next. A point-by method that was universal at one group may have an alternate method at another. A schedule that looked like a loose outline at one track may be the difference between making grid calmly and missing your session at another. The reading skill is to translate the packet into an operating plan for your day.
Start with the purpose of HPDE. The corpus is consistent on this point: HPDE is education, not competition. PCA minimum standards describe HPDE as having no award points and no trophies. The SEM PCA beginners guide says PCA DE events are not racing and are not preparation for racing, with no times or placings recorded and no awards or prizes given. That matters because it changes how you read the event. You are not reading it to discover how to win the day. You are reading it to discover how to enter a controlled learning environment without creating avoidable friction for yourself, your instructor, the organizer, or other drivers.
The event packet is your first instruction session. A good schedule is not just a list of times. SCCA rules say schedules should show planned groups, how much time or how many runs entrants are scheduled to receive, the times and locations of mandatory inspections or meetings, novice classrooms, novice debriefs, and driver experience groupings. If the schedule is separate from the event page, it should also identify the event name, location, and date. Read those fields as commitments. If your group has four sessions and a classroom, that gives you the shape of your learning day. If your meeting is mandatory and at a specific location, that is not optional background information. If your run group rotates with others, the schedule becomes the spine of your paddock rhythm.
Build your event brief in four passes. Pass one is identity and eligibility: who is organizing, where the event is, what date it is, what car you are registered in, what run group you are assigned, whether you meet the age and license requirements, and whether your helmet and car fit the event rules. Pass two is movement: when you need to arrive, where registration, tech, drivers meeting, classroom, grid, fuel, and paddock are, and which times are hard stops. Pass three is risk: what can keep you from getting on track, including missing tech paperwork, an expired or wrong helmet rating, unread supplemental rules, illegible numbers, convertible restrictions, equal-safety requirements for instructor seating, or local safety equipment requirements that exceed the generic minimum. Pass four is learning: what you should study before arrival, what track map or video will help you recognize the facility, which classroom sessions or debriefs matter, and what feedback forms or review sheets show the organizer cares about.
This is not paperwork theater. The sources repeatedly treat advance preparation as part of safety and learning. NASA material tells entrants they are expected to know the applicable rules in the Club Codes and Regulations. SCCA warns that some locations and events may require different minimum standards from the general rules and cautions participants to carefully read the supplementary regulations for the event they intend to enter. BMW CCA Rocky Mountain tells drivers to check their registration, print schedules and tech forms, schedule tech now because service items may require time to resolve, make sure helmets meet minimum standards, get numbers and letters for both sides of the car, prepare personal items, bring water, and complete required reading. NASA Texas tells drivers to have the car teched before arrival, bring the tech sheet, study the track map, use video, simulator driving, and karting as preparation, and hydrate after each session. Those are not random tips. They are the operating system of a clean HPDE day.
Here is the principle: read the event until every required action has either been done, scheduled, packed, or written into your event brief. If a sentence in the packet implies an action, capture the action. If it says the car must be teched within a specific window, your action is not remember tech. Your action is book tech early enough that a failed inspection can still be repaired. If it says bring the tech sheet, your action is print it, photograph it, and put the paper copy where it will travel with the car. If it says numbers must be visible, your action is install numbers before the morning rush and check them from several car lengths away. If it says the drivers meeting covers facility-specific issues, your action is arrive early enough that you are not walking in while it starts.
The mechanism is simple. HPDE days run on compression. Many drivers, cars, instructors, staff, and run groups are trying to use the same facility in a fixed number of hours. A small uncertainty at home becomes a large delay at the track because every solution has a queue around it. A missing tech sheet is not just a missing sheet; one NASA packet says you will have to re-tech your car on site if you forget it. A helmet that does not meet the event standard is not just a shopping problem; it can end your track time before it starts. A schedule you did not read is not just an inconvenience; it can cause you to miss a mandatory meeting, miss classroom, or arrive late to grid and spend your first session mentally behind the car.
Read in layers, not straight through once. The BMW CCA student manual tells first-time school drivers to read all the information, not expect to absorb everything, and read it again after the school to reinforce what happened at the track. That is good advice even for an intermediate driver. On the first read, you are identifying what kind of event this is and where the major obligations live. On the second read, you are extracting action items. On the third read, ideally the night before, you are checking whether the packet still matches your plan: car, group, arrival, paperwork, water, helmet, numbers, meetings, classroom, and first-session timing. After the event, reread the key sections while the day is fresh. Procedures that looked abstract before the event will now attach to lived experience.
Use the schedule as a map of decisions. A schedule should tell you planned groups and the amount of track time or number of runs you are expected to receive. For an intermediate driver, that lets you plan energy, tires, fuel, food, water, note-taking, and instructor conversations. If you have four runs, do not spend the first two discovering basic logistics. If there is a classroom before your second run, plan your first debrief so you can get to class, not so you are still unpacking a lap when the classroom starts. If a novice debrief or meeting is listed and you are in a lower group, treat it as part of the driving, not as an optional lecture. The track session gives you data. The debrief turns that data into the next session plan.
Also read the schedule for conflict. Ask: when is registration open, when is tech inspection open, when is the drivers meeting, when does my group go to grid, and what must happen before that? If tech opens at 7:00 and the drivers meeting is at 8:00, you cannot plan to solve a paperwork problem at 7:55. If your group is early in the rotation, your car needs to be ready before the all-hands meeting, not after. If your classroom is immediately after a session, pack a notebook, water, and pen where you can grab them without digging through the trunk. If the organizer posts separate PDFs for schedule, tech, rules, and supplemental regulations, put them in one folder before you travel. The packet may be split across pages, but your event plan should not be.
The next sub-skill is rule triage. You are not trying to memorize a national rulebook in one sitting. You are trying to identify the rules that affect your participation at this event. The NASA NorCal acceptance package expects drivers to know applicable CCR rules. SCCA rules warn that supplementary regulations may add requirements. PCA national standards describe host-region responsibilities and the noncompetitive nature of the event. A structured index in the corpus separates guides, rulebooks, tech forms, schedules, classroom materials, medical forms, and evaluations. Use that same separation. Rules answer what must be true. Guides answer what to do. Forms answer what proof must be presented. Schedules answer when and where. Evaluation sheets answer what behavior the organizer or instructor may be watching.
Do not treat minimum standards as best practice. SCCA states that there is a considerable gap between a minimum standard and the best protection current technology can provide, and recommends that safety equipment meet the highest safety standards possible. For this lesson, the driving action is not to buy everything expensive. The action is to notice the difference between legal minimum and wise preparation. If the event requires a minimum helmet rating, satisfy it. If your own risk tolerance points to newer or better gear, handle that before event week. If the facility or organizer requires standards different from the general rule set, the supplementary regulations win for your day. The driver who reads only the generic rule may arrive technically informed and still unprepared.
Tech inspection is the clearest example of reading becoming action. NASA tech instructions say that before bringing the car to the track or the tech station, you inspect each listed item, consult a tech inspector if there are questions, fill out the top of the form before going to the inspector, and understand that making sure the car is track ready is your responsibility. NCM language says the driver or owner is solely responsible for the track worthiness and safe condition of the vehicle and equipment before, during, and after the event, even when an event-related inspection exists. BMW CCA Rocky Mountain tells drivers to schedule tech now because service items may require time to resolve and notes that cars must be teched within four weeks of the event. NASA Texas warns that you will not be allowed on track unless the car has been teched and that forgetting the tech sheet means on-site re-tech.
The intermediate habit is to read the tech form as a countdown, not a receipt. A receipt says someone checked it. A countdown says this item can fail and cost me the event if I wait too long. Tires, brake pads, fluid, wheel bearings, belts, battery security, leaks, helmet rating, numbers, and paperwork may all be routine, but routine items still need time. If you read the packet three days before the event and discover a requirement for a shop inspection within a certain window, you may have left yourself no room for repair. If you read it three weeks before, the same problem is just a task.
Convertibles, instructor seating, and equal-safety language deserve careful reading because they are often not intuitive. The bonded corpus includes an appendix heading for convertibles and a NASA Texas note asking for equal safety for driver and passenger instructor sides. Even without the full convertible appendix text in the bond, the presence of the appendix is a warning: do not assume that a street-legal car is automatically track-eligible. If your car is a convertible, has modified restraints, has a roll bar, has fixed-back seats, has harnesses, or has asymmetric equipment between driver and passenger, you must read the organizer-specific rules and ask early. The wrong time to discover an instructor cannot ride safely in your passenger seat is when your run group is called.
Read the drivers meeting expectations before the drivers meeting. SCCA standards recommend that the meeting include a welcome, a reminder that drivers should work together so everyone can perform their best, event-specific flag or communication procedures, alternate point-by methods or cars using them, and track or facility-specific issues. That tells you what to listen for. You are not waiting for generic announcements. You are listening for deltas: anything different from your last event, anything specific to this facility, anything about passing signals, anything about flags, anything about where incidents tend to happen, anything about grid, pit-in, pit-out, blend line, sound limits, paddock traffic, or local facility rules.
The reason to read before the meeting is that a prepared driver can hear what is new. If the first time you think about flags is during the drivers meeting, every sentence has equal weight and the important local exception can slide by. If you already know the normal structure, you can hear the sentence that changes your behavior. SCCA explicitly calls out event-specific procedures for flags and communication signals, alternate point-by methods, descriptions of cars using them, and facility-specific issues. Make a small blank box in your event brief for meeting notes. Title it changes from packet. During the meeting, write only the changes, emphasis points, and local warnings you need to act on.
A strong event brief is short enough to use. Do not rewrite the packet. Build a one-page driver brief with these headings: event identity, arrival plan, required documents, car and gear, schedule spine, first-session plan, meeting deltas, and open questions. Under event identity, write organizer, track, date, run group, car, instructor status, and any host-region or rule-set note. Under arrival plan, write gate time, paddock target, registration location, tech location, drivers meeting location, classroom location, and grid location if known. Under required documents, write license, tech sheet, waiver, registration confirmation, helmet requirement, medical or emergency form if applicable, and any printed schedule requirement. Under car and gear, write numbers, fuel, water, chair, clothing, rain gear, sunscreen, and tools only if the packet or your prior pattern makes them relevant. Under schedule spine, copy your group sessions and mandatory meetings. Under first-session plan, write one learning objective and one operational objective. Under meeting deltas, leave blank space. Under open questions, write what you will ask the organizer before event day or at check-in.
The first-session plan should respect the course context. This lesson sits next to arriving ready to learn and using your run group correctly, so do not turn the event brief into a driving-technique notebook. Keep it pointed at event literacy. Your operational objective might be: be in grid early, belted, helmet on, instructor settled, windows set as required, and no loose items. Your learning objective might be: learn flag stations and corner names without chasing pace. The SEM PCA guide warns new drivers not to miss good learning by going too fast too soon. Even as an intermediate driver, the first run at a new event is not where you prove pace. It is where you prove you can operate cleanly inside that organizer's system.
Use pre-event study wisely. NASA Texas lists track map review, YouTube, simulator driving, and karting as ways to study or prepare for the track. For this specific lesson, the point is not to become a hero from video. The point is to arrive oriented. A track map lets you know whether the instructor means Turn 5, the kink, pit-in, or the carousel. Video can show where pit-out blends, where flag stations sit, how the front straight looks from the driver's seat, and where the paddock entry might be. Simulator driving can help your mind and body rehearse the sequence of corners. Karting can sharpen general timing and awareness. Use all of that as orientation, then let the actual instructor, conditions, event rules, and your run group set the real pace.
Hydration and personal preparation are event-reading issues, not lifestyle advice. NASA Texas tells drivers to bring water and hydrate after each session. BMW CCA Rocky Mountain recommends a reusable water bottle and at least one gallon of water per person per day, plus personal checklist items such as sunscreen, hat, lip balm, rain gear, and related supplies. Read those lines as performance requirements. A dehydrated, sunburned, hungry, rushed driver processes less information. HPDE learning depends on attention. If your body is behind by lunch, your event brief can be perfect and your driving still gets worse.
The packet also tells you whom to ask. The SEM PCA beginners guide tells drivers to contact the DE chair or chief instructor with further questions or concerns, with contact information on the club website. That is a model for closing uncertainty early. If your event brief has open questions after two careful reads, send them before the event. Ask concrete questions: my car has this equipment, does it satisfy your instructor-side requirement? My helmet is this rating and date, is it accepted? I am registered in this car but may need to switch, what is the deadline? I cannot find the classroom location, where is it? Vague questions get vague reassurance. Specific questions get operational answers.
Intermediate drivers should also read for organizational culture. The sources show different event ecosystems: NASA, SCCA, PCA, BMW CCA, NCM, Chin, Hooked on Driving, OnGrid, and others appear across the structured guide and index. Some documents are rulebooks and standards, some are participant guides, some are tech forms, some are classroom schedules, some are feedback forms. A driver who moves among organizations must be bilingual. The same broad sport can use different run group names, different tech proof, different classroom expectations, different passing methods, different document locations, and different communication tone. You do not need cynicism. You need curiosity and attention.
Look for evidence of evaluation. The structured guide points to NASA Great Lakes HPDE1 session review sheets, instructor evaluation forms, and student evaluation forms. Even if your event does not use those exact forms, their presence in the HPDE ecosystem tells you that learning is observed and structured. If you can find a review sheet before the event, read it. It shows the behaviors instructors may mark: awareness, control, consistency, flag response, line, smoothness, or readiness for the next group. Do not overfit your day to a form. Use it to understand what safe progress looks like to the organizer.
The hardest part of this skill is humility. You may already know how to drive a clean line. You may know your local track. You may know flags and point-bys. But the event packet is not asking whether you are generally knowledgeable. It is asking whether you are prepared for this organizer, this facility, this day, this group, this car, and this set of rules. The driver who reads well arrives with less drama and more spare attention. Spare attention is what you need for the actual learning.
A good pre-arrival read produces visible outcomes. You show up with the correct car registered, the tech form completed, the helmet accepted, the numbers legible, the waiver handled if applicable, the schedule printed or saved, the first meeting location known, water packed, and the first run group timing understood. You know what documents to present and where. You know what you still need to ask. You know the event is noncompetitive, so your first measure of success is clean participation, not pace. You know that local supplemental rules may matter more than assumptions from your last club. You know that the drivers meeting may contain event-specific procedures, alternate point-by notes, and facility-specific issues, so you listen for them.
A poor pre-arrival read also produces visible outcomes. You arrive with a car different from the registration. You cannot find your tech sheet. Your helmet standard is wrong or uncertain. Your numbers are too small or hard to see. You miss a meeting location. You skip classroom because you thought it was optional. You learn a passing rule while already strapped in. You use the first session to orient to pit-out, flag stations, and paddock flow that you could have studied earlier. None of those errors prove you are careless. They prove your reading method did not convert text into action.
Use this lesson's central rule every time you register: the event starts when the packet arrives, not when the green flag waves. Registration confirms your intent. Reading converts intent into readiness. Your first lap is built from all the little decisions you made before you left home: whether the car was inspected in time, whether the paperwork is in the glove box, whether the schedule is understood, whether the meeting details are known, whether you asked the question that was bothering you, whether you drank water after the last session, whether you remembered that HPDE is education. Read that way, and the event stops feeling like a pile of documents. It becomes the first half of your driving plan.
Worked example: BMW CCA Rocky Mountain packet to paddock plan
Suppose you register for a BMW CCA Rocky Mountain driving school. The preparation guide gives you a direct pre-event checklist. It tells you to make sure you are old enough and have a valid driver license, check MotorsportReg to confirm the car you intend to drive is the car in your registration, print copies of the driving school schedule, print copies of the tech inspection form, schedule tech now because service items may require time to resolve, make sure the helmet meets minimum standards, get numbers and letters for both sides of the car, prepare personal items, bring water, complete required reading, and consider the digital waiver and profile picture.
A weak read turns that into a vague reminder to get ready. A strong read turns it into dated tasks. Three to four weeks out, you confirm the registered car, book tech, and inspect the helmet standard. Two weeks out, you solve any service items and order or make car numbers. The week of the event, you print or save the schedule and tech form, put one paper copy in the car, and pack the personal checklist. The night before, you check the schedule against your arrival target and lay out the documents you will present. The morning of the event, you are not asking what to do first. The packet already answered that.
Notice how much control this gives you. If tech finds a problem early, it is a repair. If tech finds the problem at the gate, it may be the end of your track time. If the schedule is in your brief, you can choose when to eat, hydrate, talk to your instructor, and head to grid. If the schedule is something you open for the first time in the paddock, every next step competes with noise, nerves, and other drivers trying to solve their own problems.
Worked example: NASA Texas welcome packet to first-session readiness
Now imagine a NASA Texas HPDE welcome packet for Texas Motor Speedway. The packet says to have the car teched before arrival, warns that you will not be allowed on track unless the car has been teched, tells you to bring the tech sheet, and says you will have to re-tech on site if you forget it. It also says to look over the track map, use YouTube as a look at the track, consider simulator driving, consider karting, and bring water and hydrate after each session.
For an intermediate driver, the important move is to separate hard requirements from useful orientation. The hard requirement is tech proof. That gets handled first, with redundancy: paper in the car, photo on the phone, and confirmation that the form is complete. The orientation work comes next. You study the track map to learn the sequence and facility names. You watch video for pit-out, pit-in, flag stations, and the visual approach to major corners. You may use a simulator to rehearse the order of turns, but you do not treat simulator pace as a promise. You pack water because the packet explicitly tells you to hydrate after each session.
The result is a calmer first session. You already know the track has a shape. You already know where your paperwork is. You already know hydration is part of your between-session routine. Your instructor can spend the first session teaching how to drive the facility instead of helping you recover from avoidable logistics.
Common mistakes
The first mistake is reading only the schedule. The schedule matters, but it is only one layer. The rules and supplemental regulations may contain equipment, passing, meeting, or facility requirements that the schedule will not repeat. Good looks like reading the event page, downloadable schedule, tech form, rules, and supplemental notes as one packet.
The second mistake is treating tech inspection as somebody else's responsibility. The NASA form language and NCM acknowledgement both put responsibility on the driver or owner for track worthiness and safe condition. Good looks like inspecting the listed items before the event, asking a tech inspector when uncertain, scheduling the inspection early enough to repair problems, and carrying the completed form.
The third mistake is assuming last event's rules apply. SCCA explicitly warns that some locations and events may require different minimum standards than the general rules. Good looks like reading the supplementary regulations for the specific event you intend to enter and marking anything that differs from your last organizer.
The fourth mistake is listening passively in the drivers meeting. SCCA describes drivers meeting content that may include event-specific flag procedures, alternate point-by methods, and facility-specific issues. Good looks like arriving already familiar with the basics, then writing down the deltas that change how you will drive that day.
The fifth mistake is using pre-event video to build confidence instead of orientation. NASA Texas recommends track maps, YouTube, simulator driving, and karting as preparation, but the event is still a live learning environment. Good looks like using video to recognize pit-out, flag stations, corner sequence, and sight pictures, then letting conditions, instructor guidance, and run-group rules set your actual pace.
The sixth mistake is skipping personal preparation because it feels less technical. The preparation guide recommends water, sunscreen, hat, lip balm, rain gear, and related items; NASA Texas tells drivers to hydrate after each session. Good looks like treating your body as part of the system you are bringing to the track. You cannot learn well if you are dehydrated, overheated, or scrambling for basics between sessions.
Drill: the 30-minute event packet conversion
Do this drill for your next HPDE, even if you think you know the organizer. Set a timer for 30 minutes and create a one-page event brief from the actual event documents. Use five blocks.
For the first five minutes, capture identity: organizer, track, date, run group, registered car, rule set, and any host or facility note. For the next eight minutes, capture hard requirements: license, waiver, tech form, helmet standard, car numbers, instructor-side or equal-safety notes, convertible or vehicle-specific restrictions, and anything that says mandatory. For the next seven minutes, capture movement: arrival time, registration, tech, drivers meeting, classroom, grid, pit-out, and your run sessions. For the next five minutes, capture learning prep: track map, video, simulator or karting if useful, required reading, and one first-session objective. For the final five minutes, write open questions and send any that can be answered before the event.
The success criterion is concrete. When the timer ends, every requirement from the packet is either done, scheduled, packed, or written as a question to ask. If you cannot say that, you have not finished reading the event; you have only looked at it.
Cross-references
This lesson supports the sibling lesson on arriving ready to learn because event reading is how you turn general readiness into event-specific readiness. It also supports the lesson on using your run group correctly because the schedule, group assignment, classroom timing, and drivers meeting notes define how your group operates that day. Keep the boundary clear: this lesson teaches how to extract and act on event information before arrival. The next step is executing that plan in the paddock, classroom, grid, and run group without letting pace or ego outrun the event structure.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | HPDE Verbatim Master Compilation | db008222-d922-9b58-8534-cf76f4993100 | 274 | 1 | uio_books_raw_v1 |
| 2 | HPDE Verbatim Master Compilation | ea93a760-ac87-9af7-2c8b-b8c53b984685 | 161 | 1 | uio_books_raw_v1 |
| 3 | HPDE Verbatim Master Compilation | 7c91ac8b-38e1-52ca-0496-14a34a79008f | 121 | 1 | uio_books_raw_v1 |
| 4 | HPDE Verbatim Master Compilation | 54c5c32b-3808-8951-08c9-5a1dc879b557 | 140 | 1 | uio_books_raw_v1 |
| 5 | HPDE_Verbatim_Master_Compilation | f0246f9be085acb826e39ef8c456a96d | 173 | 1 | uio_books_raw_v1 |
| 6 | HPDE Verbatim Master Compilation | d148731f-e86b-5f38-4f21-b593708a08b9 | 167 | 1 | uio_books_raw_v1 |
| 7 | HPDE Verbatim Master Compilation | 881e3857-c9c0-95a8-fbcc-f32d8dcc8cea | 1 | 1 | uio_books_raw_v1 |
| 8 | HPDE Verbatim Master Compilation | 15ec5b3e-d67f-a4a1-bd1c-30a2261802d1 | 349 | 1 | uio_books_raw_v1 |
| 9 | HPDE Verbatim Master Compilation | 4592689b-9768-5492-17e5-e1ba712380fd | 242 | 1 | uio_books_raw_v1 |
| 10 | HPDE Verbatim Master Compilation | ca0a03e8-6761-f578-8d84-2c63329ed783 | 114 | 1 | uio_books_raw_v1 |
| 11 | HPDE Verbatim Master Compilation | 0f4fc391-a697-e3a6-c047-936d8cf0c85c | 203 | 1 | uio_books_raw_v1 |
| 12 | HPDE_Structured_Guide_and_Index | 6fbecf31ea03dae1bca830ff870adb37 | 1 | 1 | uio_books_raw_v1 |
| 13 | HPDE_Structured_Guide_and_Index | a49877d5206a243d5c9a44be8c94d26e | 8 | 1 | uio_books_raw_v1 |
| 14 | HPDE_Structured_Guide_and_Index | cb1d8668adf1abbc7a8d2e36faae93e2 | 24 | 1 | uio_books_raw_v1 |
| 15 | The HPDE 1st Timer s Guide - Ross Bentley | b2d9ba53-51a6-ba2b-fbd0-e601d7ef2399 | 25 | 1 | uio_books_raw_v1 |
| 16 | HPDE Verbatim Master Compilation | 45252e3a-6bb3-7b83-8c38-e591cc19f0e7 | 261 | 1 | uio_books_raw_v1 |
| 17 | HPDE Verbatim Master Compilation | b90a37df-a6b5-6ed7-981c-8063cf83ae5c | 274 | 1 | uio_books_raw_v1 |
| 18 | HPDE Verbatim Master Compilation | fd9b240c-5c00-4d4a-8077-ea34c34b2d44 | 271 | 1 | uio_books_raw_v1 |