Repository navigation
Conversation
…connector API Main changed the connector API. A label set carries its name as an annotation, a Hugging Face connector passes its Hub settings as class keywords and reads a mapping from part to path, BaseConnector names the whole download result, and Annotation takes its value by keyword.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a connector for CARE to Compare (Fraunhofer IEE), a real-world benchmark for early fault detection in wind turbine SCADA data. It is the first energy/industrial dataset in the catalog.
Source
ca61379e…94f1), from a download whose MD5 matches the one Zenodo publishes (2547b58c…500c).What the dataset holds
RegularAxis, plus the turbine's operating status (status_type_id). Skipped grid steps and empty cells are nulls. Units map to pint where unambiguous; otherwise the release string is kept as asource_unitannotation.training_period,prediction_period, and theevent_windowinterval.ClassificationTask(event_label: anomaly / normal) scoped to the prediction period, for every Record.TemporalLocalizationTasktargeting theevent_windowannotation, for every anomaly Record.ClassificationTask(fault_component) for the 18 anomaly events of farms A and B, derived from the release's root-cause notes (documented on the card as TimeNet-derived).Implementation notes
source.pyparses and validates the release: header, row IDs, the 10-minute grid, a single asset per file, training rows before prediction rows, and event windows on the grid. It has no TimeNet types, so it is tested on its own.sensor_44tosensor_51) without a statistic suffix. They read as their sensor's single statistic. All three farms' headers were checked against their feature descriptions.connector.pycaches each event's values as a feature-major.npynext to the extracted CSV and builds Signals withSignal.from_loader, so a build holds one event in memory at a time (wind farm C alone is about 17.8 GB of CSV).Verification
pyteston the connector tests: 13 passed.ruff format,ruff checkandty checkare clean on the new package.TimeFDataset.write, then read back withTimeFReader.verify(): 22 Records × 82 Signals, 34 classification and 12 localization tasks. The labels (12 anomaly / 10 normal; 6 hydraulic, 3 gearbox, 2 generator bearing, 1 transformer) match the release's event table. Conversion took 76 s on a 2-core Codespace, and the written version is 84 MB.timenet-build build fraunhofer-iee/care-to-compareover all three farms. Wind farm C needs roughly 40 GB of free disk for extraction and cache.