<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Conferences on Markus Löning</title><link>https://www.mloning.com/tags/conferences/</link><description>Recent content in Conferences on Markus Löning</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2025 Markus Löning</copyright><lastBuildDate>Mon, 06 Jul 2026 18:03:47 +0200</lastBuildDate><atom:link href="https://www.mloning.com/tags/conferences/index.xml" rel="self" type="application/rss+xml"/><item><title>EurIPS 2025</title><link>https://www.mloning.com/posts/eurips-2025/</link><pubDate>Tue, 02 Dec 2025 11:33:55 +0100</pubDate><guid>https://www.mloning.com/posts/eurips-2025/</guid><description>&lt;p&gt;I attended EurIPS 2025 in Copenhagen, the first edition of the European version of NeurIPS.
My notes are mainly about topics related to my current work, that is, time series analysis and biosignals.&lt;/p&gt;</description></item><item><title>EuroRust 2025</title><link>https://www.mloning.com/posts/eurorust-2025/</link><pubDate>Sat, 11 Oct 2025 11:58:15 +0200</pubDate><guid>https://www.mloning.com/posts/eurorust-2025/</guid><description>&lt;p&gt;I attended my first Rust conference, &lt;a href="https://eurorust.eu/2025/"&gt;EuroRust 2025&lt;/a&gt; in Paris.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;clippy settings recommendations, including &lt;code&gt;pedantic&lt;/code&gt; or &lt;code&gt;undocumented_unsafe_blocks&lt;/code&gt; (structured safety documentation) for unsafe code&lt;/li&gt;
&lt;li&gt;best practices for Rust development by jhpratt (&lt;a href="https://jhpratt.dev/talks/#exemplary-by-design-building-and-maintaining-rust-at-scale"&gt;slides&lt;/a&gt;, also see his related talk on &lt;a href="https://jhpratt.dev/talks/#compiler-driven-development-making-rust-work-for-you"&gt;compiler-driven development&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;inner workings of the Rust compiler, compiler settings and their trade-offs including inlining, &lt;a href="https://en.wikipedia.org/wiki/Monomorphization"&gt;monomorphization&lt;/a&gt; link-time optimizations (LTO) by noratrieb (&lt;a href="https://noratrieb.dev/slides/2025-10-10-how-rust-compiles/"&gt;slides&lt;/a&gt;, &lt;a href="https://nnethercote.github.io/perf-book/"&gt;Rust performance book&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;best practices for error handling: for anticipated errors, prefer &lt;code&gt;thiserror&lt;/code&gt; for libraries to expose concrete and structured errors, and &lt;code&gt;Result&lt;/code&gt; type and &lt;code&gt;anyhow&lt;/code&gt; for application code, for unanticipated errors use &lt;code&gt;panic!&lt;/code&gt; (programmer mistake)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;criterion&lt;/code&gt; and flamegraphs for profiling&lt;/li&gt;
&lt;li&gt;inner working of atomic types for concurrency and &lt;a href="https://en.wikipedia.org/wiki/Memory_ordering"&gt;memory ordering&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;prefer concrete types (e.g. enums) over generics and traits, for speed due to monomorphization and readability, especially in application code&lt;/li&gt;
&lt;li&gt;&lt;a href="https://mfontanini.github.io/presenterm/"&gt;presenterm&lt;/a&gt; for making presentations in your terminal&lt;/li&gt;
&lt;li&gt;&lt;code&gt;embassy&lt;/code&gt; for embedded systems&lt;/li&gt;
&lt;li&gt;&lt;code&gt;bevy&lt;/code&gt; game engine&lt;/li&gt;
&lt;li&gt;the concept of run-time &lt;a href="https://en.wikipedia.org/wiki/Reflective_programming"&gt;reflection&lt;/a&gt; and and Rust&amp;rsquo;s compile-time solutions based on procedural macros like &lt;code&gt;serde&lt;/code&gt;&amp;rsquo;s &lt;code&gt;derive&lt;/code&gt;, e.g. when you add &lt;code&gt;#[derive(Serialize, Deserialize)]&lt;/code&gt; to a struct, you are using a procedural macro that runs when you compile your code; the macro inspects the definition of your struct (e.g., the field names and types), and based on this inspection automatically generates the implementation of the core &lt;code&gt;Serialize&lt;/code&gt; and &lt;code&gt;Deserialize&lt;/code&gt; traits for your specific type&lt;/li&gt;
&lt;li&gt;triemap, a tree-based data structures primarily used for efficient storage and retrieval of associative data where the keys are strings or sequences, e.g. for fast prefix-based lookup&lt;/li&gt;
&lt;li&gt;foreign function interfaces (FFI) in Rust for using functions from other programming languages, particularly C (e.g. using &lt;code&gt;extern&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://valgrind.org/"&gt;Valgrind&lt;/a&gt; for profiling and memory debugging&lt;/li&gt;
&lt;li&gt;data engineering
&lt;ul&gt;
&lt;li&gt;OLAP (analytical)
&lt;ul&gt;
&lt;li&gt;batch operations involving complex queries, aggregations and scans across many rows but few columns&lt;/li&gt;
&lt;li&gt;primarily columnar data format, e.g. Parquet/Arrow&lt;/li&gt;
&lt;li&gt;data warehouse solutions like Delta Lake and Snowflake&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;OLTP (operational)
&lt;ul&gt;
&lt;li&gt;frequent inserts, updates, deletes, and fetching full records (e.g. banking transactions, user profiles)&lt;/li&gt;
&lt;li&gt;row-based format (e.g. PostgreSQL)&lt;/li&gt;
&lt;li&gt;document-based/NoSQL databases (e.g. MongoDB), better for complex entities to avoid complicated SQL joins&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Videos will be available at: &lt;a href="https://www.youtube.com/@eurorust"&gt;https://www.youtube.com/@eurorust&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Pydata Paris 2025</title><link>https://www.mloning.com/posts/pydata-paris-2025/</link><pubDate>Thu, 02 Oct 2025 11:58:15 +0200</pubDate><guid>https://www.mloning.com/posts/pydata-paris-2025/</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;code&gt;quarto&lt;/code&gt; for publication-ready reports and presentations (see e.g. &lt;a href="https://github.com/paddyroddy/talks"&gt;https://github.com/paddyroddy/talks&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;an overview of the array API standard by Lucas Colley&lt;/li&gt;
&lt;li&gt;optimal transport theory and Python library (&lt;a href="https://github.com/PythonOT/POT"&gt;https://github.com/PythonOT/POT&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;free-threaded Python rollout (see &lt;a href="https://labs.quansight.org/blog/free-threaded-python-rollout"&gt;https://labs.quansight.org/blog/free-threaded-python-rollout&lt;/a&gt;, &lt;a href="https://lwn.net/Articles/1025893/"&gt;https://lwn.net/Articles/1025893/&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;conflict-free replicated data type (CRDT) for lock-free concurrent read/write access, they don&amp;rsquo;t need locks because they accept conflicts but define rules (&amp;ldquo;merge&amp;rdquo; operations) that resolve conflicts (e.g. used collaborative text editors like Google Docs) (see &lt;a href="https://read.thecoder.cafe/p/crdt"&gt;https://read.thecoder.cafe/p/crdt&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;met the maintainer of tslearn, @charavelg&lt;/li&gt;
&lt;li&gt;Introductory talk on prediction intervals and quantile regression based on scikit-learn, but interface seems incomplete, more complete interfaces exists&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Talks are available on &lt;a href="https://www.youtube.com/playlist?list=PLGVZCDnMOq0rXq5aghELxbd-QgL8uyg0p"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>