Northern pygmy mouse

The northern pygmy mouse (Baiomys taylori)[2] is a species of rodent in the family Cricetidae. It is known as ratón-pigmeo norteño in the Spanish-speaking areas of its range. It is found in Mexico and the United States.

Northern pygmy mouse

Least Concern  (IUCN 3.1)[1]
Scientific classification
Kingdom: Animalia
Phylum: Chordata
Class: Mammalia
Order: Rodentia
Family: Cricetidae
Subfamily: Neotominae
Genus: Baiomys
Species:
B. taylori
Binomial name
Baiomys taylori
(Thomas, 1887)

Parasites of the northern pygmy mouse include the intestinal nematode Pterygodermatites baiomydis.[3] The average size of an adult male is approximately 7.5 grams, while adult females can weigh up to 9.4 grams.[4]

Reproduction

The pygmy mouse has litters of 1 to 5 pups, with an average size of 3.[4] The gestation time for pregnant females is less than 20 days.[4] Unlike many other rodents, father pygmy mice will care for offspring, and groom and huddle over young.[4]

Communication

In captivity, these mice will sometimes produce a 'squeal', and use a posture similar to singing mice.[4]

gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
gollark: If you run too much current through beans they may vaporise/burn/etc.
gollark: You could make a mechanical computer from solidified beans.
gollark: Can beans be used for digital logic?

References
  1. Timm, R.; Álvarez-Castañeda, S.; Castro-Arellano, I. & Lacher, T. (2008). "Baiomys taylori". IUCN Red List of Threatened Species. 2008. Retrieved 18 July 2009.CS1 maint: ref=harv (link) Database entry includes a brief justification of why this species is of least concern.
  2. Musser, G. G. and M. D. Carleton. 2005. Superfamily Muroidea. pp. 894–1531 in Mammal Species of the World a Taxonomic and Geographic Reference. D. E. Wilson and D. M. Reeder eds. Johns Hopkins University Press, Baltimore.
  3. Lynggaard C, García-Prieto L, Guzmán-Cornejo C & Osorio-Sarabia D (2014): Pterygodermatites (Paucipectines) baiomydis n. sp. (Nematoda: Rictulariidae), a parasite of Baiomys taylori (Cricetidae). Parasite, 21, 58. doi:10.1051/parasite/2014057 PMID 25375029
  4. Blair, W. Frank (November 1941). "Observations on the Life History of Baiomys Taylori Subater". Journal of Mammalogy. 22 (4): 378. doi:10.2307/1374930.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.