The dataset viewer is not available for this subset.
Exception: SplitsNotFoundError
Message: The split names could not be parsed from the dataset config.
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
for split_generator in builder._split_generators(
~~~~~~~~~~~~~~~~~~~~~~~~~^
StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 101, in _split_generators
pa_table = next(iter(self._generate_tables(**splits[0].gen_kwargs, allow_full_read=False)))[1]
~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 343, in _generate_tables
self._cast_table(pa_table, json_field_paths=json_field_paths),
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 136, in _cast_table
pa_table = table_cast(pa_table, features.arrow_schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2312, in cast_table_to_schema
cast_array_to_feature(
~~~~~~~~~~~~~~~~~~~~~^
table[name] if name in table_column_names else pa.array([None] * len(table), type=schema.field(name).type),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
feature,
^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 1861, in wrapper
return pa.chunked_array([func(chunk, *args, **kwargs) for chunk in array.chunks])
~~~~^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2118, in cast_array_to_feature
casted_array_values = _c(array.values, feature.feature)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 1863, in wrapper
return func(array, *args, **kwargs)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2071, in cast_array_to_feature
return pa.StructArray.from_arrays(arrays, names=list(feature), mask=array.is_null())
~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "pyarrow/array.pxi", line 4386, in pyarrow.lib.StructArray.from_arrays
File "pyarrow/array.pxi", line 1877, in pyarrow.lib.Array.validate
check_status(self.ap.Validate())
File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
raise convert_status(status)
pyarrow.lib.ArrowInvalid: Struct child array #1 invalid: Invalid: Length spanned by list offsets (1303773) larger than values array (length 1303745)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 68, in compute_split_names_from_streaming_response
for split in get_dataset_split_names(
~~~~~~~~~~~~~~~~~~~~~~~^
path=dataset,
^^^^^^^^^^^^^
config_name=config,
^^^^^^^^^^^^^^^^^^^
token=hf_token,
^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
info = get_dataset_config_info(
path,
...<6 lines>...
**config_kwargs,
)
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
Mirror of facebook/SA-FARI. All credit to the original authors. Not an official release from them. License unchanged (SAM License); see
LICENSE.
SA-FARI Dataset
License CC-BY-NC 4.0
SA-FARI is a wildlife camera dataset collected through a collaboration between Meta and CXL.
All videos and pre-processed JPEGImages can be found in cxl-public-camera-trap, which contains the following contents:
sa_fari/
├── sa_fari_test_tars/
│ ├── JPEGImages_6fps/
│ ├── videos/
├── sa_fari_test/
│ ├── JPEGImages_6fps/
│ ├── videos/
├── sa_fari_train_tars/
│ ├── JPEGImages_6fps/
│ ├── videos/
└── sa_fari_train/
├── JPEGImages_6fps/
└── videos/
videos: The original full fps videos.JPEGImages_6fps: For annotation, the videos have been downsampled to 6fps. This folder contains the downsampled frames compatible with the annotation json files below.
This Hugging Face dataset repo contains the annotations:
datasets/facebook/SA-FARI/tree/main/
└── annotation/
├── sa_fari_test.json
├── sa_fari_test_ext.json
├── sa_fari_train.json
└── sa_fari_train_ext.json
sa_fari_test.jsonandsa_fari_train.json- Follow the same format as SA-Co/VEval
sa_fari_test_ext.jsonandsa_fari_train_ext.json- In additional to the [SA-Co/VEval] format, we added additional metadata to the following fields:
videos:video_num_frames,video_fps,video_creation_datetimeandlocation_idhave been added as additional metadata to thevideosfield.
categories:Kingdom,Phylum,Class,Order,Family,GenusandSpecieshave been added when applicable as additional metadata to thecategoriesfield.
- In additional to the [SA-Co/VEval] format, we added additional metadata to the following fields:
All the SA-FARI annotation files are compatible to use the visualization notebook and offline evaluator developed in SAM 3 Github.
Annotation Format
A format breakdown for sa_fari_test.json and sa_fari_train.json. The format is similar to the YTVIS format.
In the annotation json, e.g. sa_fari_test.json there are 5 fields:
- info:
- A dict containing the dataset info
- E.g. {'version': 'v1', 'date': '2025-09-24', 'description': 'SA-FARI Test'}
- videos
- A list of videos that are used in the current annotation json
- It contains {id, video_name, file_names, height, width, length}
- annotations
- A list of positive masklets and their related info
- It contains {id, segmentations, bboxes, areas, iscrowd, video_id, height, width, category_id, noun_phrase}
- video_id should match to the
videos - idfield above - category_id should match to the
categories - idfield below - segmentations is a list of RLE
- video_id should match to the
- categories
- A globally used noun phrase id map, which is true across all 3 domains.
- It contains {id, name}
- name is the noun phrase
- video_np_pairs
- A list of video-np pairs, including both positive and negative used in the current annotation json
- It contains {id, video_id, category_id, noun_phrase, num_masklets}
- video_id should match the
videos - idabove - category_id should match the
categories - idabove - when
num_masklets > 0it is a positive video-np pair, and the presenting masklets can be found in the annotations field - when
num_masklets = 0it is a negative video-np pair, meaning no masklet presenting at all
- video_id should match the
data {
"info": info
"videos": [video]
"annotations": [annotation]
"categories": [category]
"video_np_pairs": [video_np_pair]
}
video {
"id": int
"video_name": str # e.g. sav_000000
"file_names": List[str]
"height": int
"width": width
"length": length
}
annotation {
"id": int
"segmentations": List[RLE]
"bboxes": List[List[int, int, int, int]]
"areas": List[int]
"iscrowd": int
"video_id": str
"height": int
"width": int
"category_id": int
"noun_phrase": str
}
category {
"id": int
"name": str
}
video_np_pair {
"id": int
"video_id": str
"category_id": int
"noun_phrase": str
"num_masklets" int
}
- Downloads last month
- 16