<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python | Stefano Blando</title><link>https://stefano-blando.github.io/en/tags/python/</link><atom:link href="https://stefano-blando.github.io/en/tags/python/index.xml" rel="self" type="application/rss+xml"/><description>Python</description><generator>HugoBlox Kit (https://hugoblox.com)</generator><language>en-US</language><lastBuildDate>Wed, 18 Mar 2026 00:00:00 +0000</lastBuildDate><image><url>https://stefano-blando.github.io/media/icon_hu_8d0dee6c10a3c598.png</url><title>Python</title><link>https://stefano-blando.github.io/en/tags/python/</link></image><item><title>Multi-Agent Orchestration</title><link>https://stefano-blando.github.io/en/projects/multi-agent-orchestration/</link><pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/projects/multi-agent-orchestration/</guid><description>&lt;p&gt;This project can be read as a system for &lt;strong&gt;real-time economic coordination&lt;/strong&gt; under changing phases, partial information, and hard timing constraints.&lt;/p&gt;
&lt;p&gt;The system is structured as an &lt;strong&gt;event-driven multi-agent orchestration layer&lt;/strong&gt;. It listens to the game through SSE events, keeps a runtime representation of the environment, and switches strategy depending on the current phase of play: policy update, procurement auction, inventory reconciliation, and fulfillment.&lt;/p&gt;
&lt;p&gt;What makes the project interesting is not just the use of multiple agents, but the way orchestration is tied to operational robustness. Different capability sets are activated at different stages, while local persistence, metrics, and replay analysis help make decisions more stable under noisy runtime conditions.&lt;/p&gt;
&lt;p&gt;In practice, it is a good example of a project where agentic design had to be grounded in execution reliability rather than in generic prompting alone. The deeper pattern is &lt;strong&gt;auction-based coordination with inventory constraints and demand handling&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="interactive-explorer"&gt;Interactive Explorer&lt;/h2&gt;
&lt;p&gt;The interactive app focuses on the engineering core of the project: the live event loop, shared runtime state, stylized agent interaction, phase-specific agents, capability partitioning, bounded memory, and KPI replay.&lt;/p&gt;
&lt;p&gt;It is intentionally presented as a &lt;strong&gt;runtime architecture explorer&lt;/strong&gt;, not as a fake benchmark dashboard. The goal is to make the orchestration logic legible in the same visual language used for the Island Model and PFSE apps, with emphasis on coordination, auctions, and fulfillment.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;
&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>PokéNexus</title><link>https://stefano-blando.github.io/en/projects/pokenexus/</link><pubDate>Wed, 04 Feb 2026 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/projects/pokenexus/</guid><description>&lt;p&gt;&lt;strong&gt;PokéNexus&lt;/strong&gt; was born from something very simple: I have loved Pokémon since I was a child, and at some point I wanted to merge that world with the kind of tools and ideas I now enjoy building with.&lt;/p&gt;
&lt;p&gt;The result is a Streamlit app that turns the Pokémon universe into an interactive space where &lt;strong&gt;graph visualization&lt;/strong&gt;, &lt;strong&gt;game mechanics&lt;/strong&gt;, and &lt;strong&gt;API-driven data&lt;/strong&gt; come together. I used &lt;strong&gt;NetworkX&lt;/strong&gt;, &lt;strong&gt;PyVis&lt;/strong&gt;, and &lt;strong&gt;Plotly&lt;/strong&gt; to explore relationships between types and entities, while &lt;strong&gt;PokeAPI&lt;/strong&gt; provides the live data layer for creatures, evolutions, and related information.&lt;/p&gt;
&lt;p&gt;Instead of being just a static graph, the project grew into a small playable system: teams can be managed, items stored, badges collected, and different progression loops layered on top of the visualization. That mix of structure, exploration, and play is exactly what made the project fun to build.&lt;/p&gt;
&lt;p&gt;It is not a research project, and it is not meant to be. It is a personal experiment where a childhood passion meets the way I now think about &lt;strong&gt;networks&lt;/strong&gt;, &lt;strong&gt;interfaces&lt;/strong&gt;, and &lt;strong&gt;interactive Python applications&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Network Topology Analysis and Machine Learning Techniques for Systemic Risk Prediction in U.S. Equity Markets</title><link>https://stefano-blando.github.io/en/publications/network-crash-prediction/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/publications/network-crash-prediction/</guid><description/></item><item><title>Advanced Recommender System</title><link>https://stefano-blando.github.io/en/projects/advanced-recommender-system/</link><pubDate>Fri, 20 Jun 2025 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/projects/advanced-recommender-system/</guid><description>&lt;p&gt;This project was developed within the &lt;strong&gt;CESMA Master&amp;rsquo;s program&lt;/strong&gt; in collaboration with &lt;strong&gt;TIM&lt;/strong&gt;. Instead of framing the problem as a standard classification task, the system was designed as a &lt;strong&gt;learning-to-rank&lt;/strong&gt; pipeline for next-best-action recommendation.&lt;/p&gt;
&lt;p&gt;That shift in framing matters because ranking is closer to the actual business decision: not just whether an action is good or bad, but which action should come first for a given user.&lt;/p&gt;
&lt;p&gt;The pipeline combines careful validation, Bayesian optimization, and ensemble ranking strategies. The end result is a substantial improvement over baseline performance on &lt;strong&gt;NDCG@5&lt;/strong&gt;, making the project a solid example of applied machine learning under realistic evaluation constraints.&lt;/p&gt;
&lt;p&gt;Performance summary:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th style="text-align: left"&gt;Stage&lt;/th&gt;
&lt;th style="text-align: left"&gt;NDCG@5 Score&lt;/th&gt;
&lt;th style="text-align: left"&gt;Improvement vs Baseline&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;Baseline Model&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;0.5030&lt;/td&gt;
&lt;td style="text-align: left"&gt;&amp;ndash;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;Best Single Model&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;0.6838&lt;/td&gt;
&lt;td style="text-align: left"&gt;+35.94%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;Best Ensemble&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;0.6852&lt;/strong&gt;&lt;/td&gt;
&lt;td style="text-align: left"&gt;&lt;strong&gt;+36.23%&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Overall, it is one of the clearest examples in the portfolio of taking a familiar ML task and reformulating it in a way that is better aligned with the actual decision problem.&lt;/p&gt;</description></item><item><title>Gas Network Risk Forecasting</title><link>https://stefano-blando.github.io/en/projects/gas-network-risk-forecasting/</link><pubDate>Fri, 01 Nov 2024 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/projects/gas-network-risk-forecasting/</guid><description>&lt;p&gt;This project was developed for the &lt;strong&gt;Hera Group Hackathon&lt;/strong&gt;, where it earned &lt;strong&gt;2nd place&lt;/strong&gt;. The task was to detect gas leak risk in a setting dominated by imbalance, sparse events, and operational uncertainty.&lt;/p&gt;
&lt;p&gt;The pipeline combines geospatial-temporal feature engineering with synthetic data augmentation through &lt;strong&gt;CTGAN&lt;/strong&gt; and &lt;strong&gt;TimeGAN&lt;/strong&gt;, then uses &lt;strong&gt;SHAP&lt;/strong&gt; to keep the final model interpretable rather than purely predictive.&lt;/p&gt;
&lt;p&gt;What I still like about this project is its balance between pragmatism and method: it is a hackathon project, but it already reflects an approach I use often, namely trying to make difficult prediction problems more robust without giving up explainability.&lt;/p&gt;</description></item><item><title>Custom Chatbot with RAG</title><link>https://stefano-blando.github.io/en/projects/rag-chatbot/</link><pubDate>Thu, 15 Feb 2024 00:00:00 +0000</pubDate><guid>https://stefano-blando.github.io/en/projects/rag-chatbot/</guid><description>&lt;p&gt;This project uses a deliberately small but structured domain to explore a larger idea: how to make language-model outputs more reliable by grounding them in retrieved context.&lt;/p&gt;
&lt;p&gt;The chatbot is built around a curated dataset of fictional characters and uses a full &lt;strong&gt;RAG&lt;/strong&gt; pipeline with embeddings, retrieval, and prompt conditioning. The dataset is playful, but the methodological point is serious: retrieval changes the behavior of the model from generic completion to context-bounded reasoning.&lt;/p&gt;
&lt;p&gt;Because the underlying data is semantically rich, the system can handle not only question answering but also character comparison, recommendation, and trait-based exploration. That makes it a useful compact example of retrieval-driven NLP design.&lt;/p&gt;</description></item></channel></rss>