Help
How importing, players and accounts actually work here — including the parts that surprise people.
Importing shots
Upload the CSV your launch monitor exports. The file is expected to have a header row naming the columns and a units row underneath it saying what those columns are measured in.
Units come from the file, not from a setting
The units row is read and every value converted to the units this app stores in — yards for distance, feet for height, miles per hour for speed, degrees for angles, rpm for spin, °F for temperature and kilopascals for air pressure. You don't have to convert anything yourself, and you don't have to tell the app which units you use.
This matters because a plausible range depends entirely on the unit. Air pressure near 101 is perfectly normal in kilopascals and impossible in inches of mercury. If the units row is missing, the app cannot tell those apart and will refuse the file rather than guess and silently store nonsense.
Importing the same file twice is safe
Each shot gets an identity derived from its own measurements, so the app recognises a shot it already has. Re-uploading a file you've already imported adds nothing. Uploading a file that overlaps another one — a week's export and then a month's export covering the same week — imports only the shots that are new.
That identity is per player and per account. Two different accounts with genuinely identical shots keep both copies; they are separate datasets that never touch.
Rows that can't be used are reported, not dropped quietly
If some rows have values outside what the declared units make possible, the import tells you which rows and which columns. A file where nothing at all is usable fails rather than reporting a successful import of zero shots.
Players
A player is a golfer whose shots are tracked. Your account can own several — you, plus anyone whose shots appear in the files you upload. If a file names "Brandon" and "Stevenson", your account gets two players and you can see both.
Renaming is always safe
A player is identified internally by a number, never by their name, so renaming disturbs nothing. Every shot, club, session and trained model stays attached. Rename freely from your players.
The same golfer as two players
The importer will not decide that "Brandon" and "Brandon He" are the same person — that is a judgement it has no business making on your behalf, and getting it wrong would silently combine two people's data. So it creates two players and leaves the decision to you.
When they are the same person, use merge. Every shot and club moves onto the player you keep. If both players hold the identical shot — the same session imported under both names — the duplicate is discarded rather than doubled, and the count is reported so you know why the total moved.
Differences in capitalisation and spacing alone are already treated as the same name, so "brandon", "Brandon" and "Brandon " match on import without any merging.
Clubs
Clubs are created from the club names in your files, one per name per player. As with players, differences of case and spacing are treated as the same club, so "7 Iron" and "7 iron" are one club and not two.
When you merge two players who each had a "7 Iron", the two become one club and its shots are combined.
Live practice
Live practice records shots as you hit them rather than importing them afterwards. A session in progress is kept as you go, so closing the tab by accident doesn't lose it — you'll be offered the pending session when you come back rather than having it silently replaced by a new one.
Clubs created during a live session match your imported clubs by the same name rules, so a live "driver" and an imported "Driver" are one club.
Your account
Your shots, players and sessions are private to your account. Nobody else can see them, and account boundaries are enforced on every query rather than by hiding links.
- Your account — see your address, change it, or sign out other devices.
- Password — changing it signs out every other browser and device but keeps you signed in here.
- Forgot your password — a reset link is sent to your address and is valid for two hours.
Changing your email address asks for your current password, and the new address has to be confirmed before it takes effect. Your old address keeps working until then, and gets told that the change was requested — so if it wasn't you, you find out while you can still do something about it.
After several wrong passwords in a row an account is locked for a short while. Waiting is the only thing that clears it; this is deliberate, and it applies to whoever is guessing as well as to you.
When something goes wrong
- The import was refused because the units row is missing
- Export again from your launch monitor without editing the file. Spreadsheet round-trips are the usual cause — opening a CSV and saving it often drops the second row or reformats the numbers.
- Some rows were rejected as out of range
- The report names the column and the value. Check the units row says what those columns are really in; a mismatch there makes otherwise fine data look impossible.
- I imported a file and nothing was added
- Those shots were already in your history. Importing the same shots twice does nothing on purpose.
- I have two of myself
- Two files spelled your name differently. Merge them.
- I can't sign in but the password is definitely right
- If your address hasn't been confirmed yet, sign-in is refused until it is — send a new link. If you have just changed your address, sign in with the new one: it is your username as well as your contact address.
- The confirmation or reset email never arrived
- Check the spam folder first. Confirmation links last 24 hours and reset links two hours, so an old one will have expired — request a fresh one rather than reusing it.
Getting help
If none of the above covers it, write to bmh178@scarletmail.rutgers.edu.