matlab-access-datafeed
>
git clone --depth 1 https://github.com/matlab/matlab-agentic-toolkit /tmp/matlab-access-datafeed && cp -r /tmp/matlab-access-datafeed/skills-catalog/computational-finance/matlab-access-datafeed ~/.claude/skills/matlab-access-datafeedSKILL.md
# Datafeed Toolbox — Bloomberg, FRED, and Haver Analytics Access financial and economic data from three major providers through the MATLAB Datafeed Toolbox. ## When to Use - User wants to connect to **Bloomberg**, **FRED**, or **Haver Analytics** from MATLAB - User needs to retrieve market data (prices, history, real-time, reference data) via Bloomberg - User needs to retrieve economic time series from the St. Louis Fed (FRED) - User needs to fetch economic/financial time series from Haver Analytics databases - User needs help choosing between interfaces within a provider (e.g., bloomberg vs blp vs bloombergHypermedia, haver vs haverview) - User is writing MATLAB code involving securities, economic indicators, or data provider connectivity ## When NOT to Use - General financial modeling or portfolio optimization that doesn't involve data provider connectivity - Bloomberg Terminal keyboard shortcuts or Excel add-in questions (not MATLAB) - Data sources not covered here (e.g., Yahoo Finance, Reuters/Refinitiv) ## Provider Overview | Provider | Data Type | Interfaces | Reference | |----------|-----------|------------|-----------| | Bloomberg | Market data (equities, fixed income, derivatives, indices) | `bloomberg`, `blp`, `bloombergHypermedia`, `bloombergEMSX` | `references/bloomberg.md` | | FRED | U.S. economic data (GDP, unemployment, CPI, interest rates) | `fredrs` (replaces obsolete `fred`) | `references/fred.md` | | Haver Analytics | Global economic & financial data (macro, industry, surveys) | `haver`, `haverdirect`, `haverview` | `references/haver.md` | ## Quick Interface Selection ### Bloomberg — see `references/bloomberg.md` for full API patterns - **Windows Desktop/Terminal user** → `bloomberg` (C++) - **Need platform independence (BPIPE)** → `bloombergBPIPE` - **Server/cloud, no Terminal (Data License)** → `bloombergHypermedia` - **Existing `blp` users** → migrate to `bloomberg` (same API, no Java needed) ### FRED — see `references/fred.md` for full API patterns - **Any platform** → `fredrs` (requires R2026a+, API key) - **`fred` is obsolete** — do NOT use it ### Haver Analytics — see `references/haver.md` for full API patterns - **Windows with local data files** → `haver` - **Windows needing remote access** → `haverdirect` - **Non-Windows / server / cloud** → `haverview` (REST API) ## How to Use References Before generating code for a specific provider, read the corresponding reference file for detailed API patterns, function signatures, gotchas, and examples: - Working with Bloomberg data → read `references/bloomberg.md` - Working with FRED economic data → read `references/fred.md` - Working with Haver Analytics data → read `references/haver.md` ## Common Rules - Always use `getSecret()` for credentials and API keys — never hardcode secrets - All three providers require the **Datafeed Toolbox** - `fredrs` additionally requires **R2026a** or later - Bloomberg and Haver local interfaces (`bloomberg`, `blp`, `haver`, `haverdirect`) are Windows-only; cloud/REST variants (`bloombergHypermedia`, `bpipe`, `haverview`, `fredrs`) are platform-independent --- Copyright 2026 The MathWorks, Inc.
>
Import recorded driving sensor data (GPS, camera, lidar, actor tracks, lanes) into scenariobuilder.* objects (GPSData, CameraData, LidarData, ActorTrackData, Trajectory, laneData) and run preprocessing — synchronize, offset correction, crop, normalizeTimestamps, convertTimestamps. Also: compute actor tracks from lidar when no annotations exist, attach camera/lidar mounting + intrinsics, export to MAT/workspace/timetable/script. Use for raw driving dataset files (KITTI, nuScenes, Waymo, Pandaset, ROS/ROS2 bags, .mat, .csv, .mp4) or driving/vehicle/sensor logs that need wrapping. drivingLogAnalyzer (DLA) is OPT-IN ONLY — invoke only on explicit user request ('DLA', 'open in DLA', 'inspect/explore/analyze the recording') or reported sensor problem (sync drift, timestamp mismatch, overlay misalignment). NEVER auto-launch DLA after wrapping (Rule 0). For 'build scenario / export to RoadRunner / drivingScenario / OpenSCENARIO / Unreal / simulate', hand off to matlab-scenario-builder.
Generate driving scenes, scenarios, road surfaces, and 3D content from already-wrapped scenariobuilder.* sensor data (GPS, camera, lidar, actor tracks) using Scenario Builder for Automated Driving Toolbox. Use to BUILD, EXPORT, or AUGMENT a virtual scenario/scene/map: ego or actor trajectories, trajectory smoothing, OpenCRG road-surface extraction, 3D asset generation, static-object placement, point-cloud georeferencing + elevation, lane-based ego localization, sensor-fusion tracking, scenario-event extraction (cut-ins, hard brakes, near-misses, ADAS disengagements), or export to RoadRunner, drivingScenario, OpenDRIVE, OpenCRG, OpenSCENARIO, or Unreal Engine. Also: log-to-scenario, scenario harvesting, accident/near-miss reconstruction, SOTIF (ISO 21448) and ISO 26262 scenario coverage, USGS-aerial-lidar scene augmentation, traffic-sign placement from camera+lidar logs. NOT for raw-data import or multi-sensor sync/crop/offset/timestamp normalization — route those to matlab-driving-data-importer.
>
>
>
>
Build, modify, and diagram SimBiology models — API reference, helper functions, and layout patterns. Use when constructing or editing models programmatically or visually.