MAP_DB(1)

✨ MAP_DB ✨

okay bestie, buckle up, because we're talking about map_db — that's the MAP_DB manual page, and it's been holding it down since September 1999. yes, the girl is a legend. 💅

🎀 NAME 🎀

map_db — reads a FASTA (0), GENBANK flat file (1), PIR/VMS (5) or GCG binary (6) sequence database and produces the offsets you need for efficient memory mapping. ✨

🌸 SYNOPSIS 🌸

map_db [-n] filename | "filename libtype"

🦋 DESCRIPTION 🦋

so like, map_db filename reads the sequence database sitting in filename and then produces a brand-new file called filename.xin 💖 — and that file is literally just the offset info you need for efficient memory mapping. no cap.

here's the tea: the programs in fasta version 32t08 can use memory mapped i/o to load sequence database files and read them efficiently. but — and this is the important part — memory mapping is used only if a ".xin" file is available. and guess who creates that ".xin" file? that's right, map_db. main character energy fr fr. 👑

also, in addition to map_db, there's list_db — she's available to display the database size, etc, plus the set of offsets calculated by map_db. so the two of them are kinda a duo. 🫶

💖 OPTIONS 💖

• -n — read the file as a DNA database. that's it. that's the whole option list. slay. 💅

💀 BUGS 💀

ngl... this section is literally empty in the original. nothing listed. no bugs to report, bestie. iconic behaviour, honestly. ✨

👑 AUTHOR 👑

Bill Pearson wrp@virginia.EDU

that's the whole thing, bestie — MAP_DB, from the September 1999 era of the manual, and you're officially caught up. go map some databases. 💜🌸🧚