Concert recording 2021-11-01

[Track 1]. Triathlon for solo horn. I. Aggressive / Paul Basler -- [Track 2]. Notturno, op. 112 / Carl Reinecke -- [Track 3]. Reflections on a Southern hymn. I. Intonation ; IV. Wondrous love / Stephen Gryc -- [Track 4]. Sunshine for horn, orchestra, and piano / Nathan Pereda -- [Track 5]. Fantasy for horn, op. 88 / Malcolm Arnold-- [Track 6]. Sonata for horn and piano / Margaret Brouwer -- [Track 7]. Tanguito / Dante Yenque -- [Track 8]. Sonata no. 3 for horn and piano / Alec Wilder -- [Track 9]. Aileron for eight horns / James Naigus -- [Track 10]. Six quartets. I. Adagio / Franz Schubert ; arranged by Verne Reynolds -- [Track 11]. Sunshine

Modelling human choices: MADeM and decision‑making

Research supported by FAPESP 2015/50122-0 and DFG-GRTK 1740/2. RP and AR are also part of the Research, Innovation and Dissemination Center for Neuromathematics FAPESP grant (2013/07699-0). RP is supported by a FAPESP scholarship (2013/25667-8). ACR is partially supported by a CNPq fellowship (grant 306251/2014-0)

Evolvix BEST Names for semantic reproducibility across code2brain interfaces

Names in programming are vital for understanding the meaning of code and big data. We define code2brain (C2B) interfaces as maps in compilers and brains between meaning and naming syntax, which help to understand executable code. While working toward an Evolvix syntax for general‐purpose programming that makes accurate modeling easy for biologists, we observed how names affect C2B quality. To protect learning and coding investments, C2B interfaces require long‐term backward compatibility and semantic reproducibility (accurate reproduction of computational meaning from coder‐brains to reader‐brains by code alone). Semantic reproducibility is often assumed until confusing synonyms degrade modeling in biology to deciphering exercises. We highlight empirical naming priorities from diverse individuals and roles of names in different modes of computing to show how naming easily becomes impossibly difficult. We present the Evolvix BEST (Brief, Explicit, Summarizing, Technical) Names concept for reducing naming priority conflicts, test it on a real challenge by naming subfolders for the Project Organization Stabilizing Tool system, and provide naming questionnaires designed to facilitate C2B debugging by improving names used as keywords in a stabilizing programming language. Our experiences inspired us to develop Evolvix using a flipped programming language design approach with some unexpected features and BEST Names at its core