archive by month
Skip to content

the critical vital absolutely essential filename question of the decade

Here is a question of virtually no importance that nevertheless has me puzzled: What should I call my learning files?

For now, Steamhammer has an opponent model file for each opponent, named om_[opponent].txt. OM for opponent model. It makes sense, or anyway it makes as much sense as an arbitrary filename can. I like names that make sense.

The next learning data I want to add is opening models, so that Steamhammer can know the timings. With knowledge of both opponent strategies and its own opening strategies, it will be able to directly compare and find counters: Your attack comes at this time, which opening is ready at that timing? It will also be able to recognize which openings are similar to others, so that when it can’t match a strategy, finding good openings by trial and error is quicker.

What should I name the opening model files? Opponent models and opening models are both empirical data, and should be updated as games are played. But the unfortunate words “opponent” and “opening” are too much alike to abbreviate nicely. Should I start with “enemy” and “build order”? “Bot” and “strategy”? Most abbreviations seem unintuitive. My best idea so far is to rename the om_* files to bot_* and use the prefix open_ for openings. Maybe OK?

What’s your idea? Because, according to the bikeshed principle, everyone should have an opinion on this....

Trackbacks

No Trackbacks

Comments

Anon / MasterFocus on :

Either "enemy/open" or "bot/open" I guess.
Your first model is about your opponent, which is your enemy and is a bot. Both options seem to indicate the subject of the model clearly enough.
Your second model is about openings, so "open" is great.

Ankmairdor on :

The most important part about building a bikeshed is comfort; why else would you want one? That said, I don't plan to ride my bike to work.
"open_" seems fine. Not that "ally_" will be a consideration anytime soon or that "human_" would be anything other than a headache; but "enemy_" seems more correct than "bot_". The enemy may not always be a bot, though it mainly fights bots in the tournament. I considered adding a single letter from "model" to them as "mBot_"/"mOpen_", but unless there are other types of files to differentiate from it doesn't add much value.

Joseph Huang on :

Just use a lightweight database like sqlite and have 1 file.

Jay Scott on :

In case of a complex access pattern, that would be the clear best way.

Add Comment

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA

Form options

Submitted comments will be subject to moderation before being displayed.