Chisle
코딩 에이전트 플러그인, 20개 실시간 작업에서 기본 모델 52% 활용, 간결한 페르소나와 출력 압축 제공
Frontier AI labs는 Labelbox 환경과 전문가 데이터를 사용해 학습합니다
Frontier AI labs train on Labelbox environments and expert data. Engineering and research teams hand their recurring work to agents on Recursion.
개발 도구Python · DockerfileGitHub @Labelbox온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
The data factory for next gen AI
README 전체를 불러오는 중입니다.
README 전문 보기 ↗With Labelbox, enterprises can easily curate and annotate data, generate high-quality human feedback data for computer vision and language models, evaluate and improve model performance, and automate tasks by seamlessly combining AI and human-centric workflows. The academic and research community also relies on Labelbox for cutting-edge AI research and experimentation.
Visit Labelbox for more information.
If you haven't already, create a free account at Labelbox.
Log into Labelbox and navigate to Account > API Keys to generate an API key.
To install the SDK, run the following command.
pip install labelbox
If you'd like to install the SDK with enhanced functionality, which additional optional capabilities surrounding data processing, run the following command.
pip install "labelbox[data]"
Please note that if you prefer to build and install your own version of the SDK, it is important to be aware that only tagged commits have been thoroughly tested. Building from the head of develop branch carries some level of risk.
After installing the SDK and getting an API Key, it's time to validate them both.
import labelbox as lb
client = lb.Client(API_KEY) # API_KEY = API Key generated from labelbox.com
dataset = client.create_dataset(name="Test Dataset")
data_rows = [{"row_data": "My First Data Row", "global_key": "first-data-row"}]
task = dataset.create_data_rows(data_rows)
task.wait_till_done()
You should be set! Running the snippet above should create a dataset called Test Dataset with its content being My First Data Row. You can log into Labelbox to verify this. If you have any issues please file a Github Issue or contact Labelbox Support directly. For more advanced examples and information on the SDK, see Documentation below.
We encourage anyone to contribute to this repository to help improve it. Please refer to Contributing Guide for detailed information on how to contribute. This guide also includes instructions for how to build and run the SDK locally.
The SDK is well-documented to help developers get started quickly and use the SDK effectively. Here are links to that documentation:
We have samples in the examples directory to help you get started with the SDK.
Make sure your notebook will use your source code:
ipython profile createipython locate - will show where the config file is. This is the config file used by the Jupyter server, since it runs via ipythonc.InteractiveShellApp.exec_lines = [
'import sys; sys.path.insert(0, "<labelbox-python root folder>")'
]
jupyter notebook to start the server.To enhance the software supply chain security of Labelbox's users, every Labelbox SDK release is built by the publish workflow and comes with signed build provenance:
multiple.intoto.jsonl) attached to the GitHub release.Verifying the provenance confirms that the package was built from this repository by our release workflow and has not been tampered with. For example, for the wheel of a given release:
export VERSION=<version> # sdk release version
export TAG=v${VERSION} # github tag
pip download --no-deps labelbox==${VERSION}
# GitHub attestation, with the GitHub CLI
gh attestation verify ./labelbox-${VERSION}-py3-none-any.whl \
--repo Labelbox/labelbox-python \
--signer-workflow Labelbox/labelbox-python/.github/workflows/publish.yml
# SLSA provenance, with slsa-verifier
curl --location -O \
https://github.com/Labelbox/labelbox-python/releases/download/${TAG}/multiple.intoto.jsonl
slsa-verifier verify-artifact --source-branch develop \
--source-uri "git+https://github.com/Labelbox/labelbox-python" \
--provenance-path multiple.intoto.jsonl ./labelbox-${VERSION}-py3-none-any.whl
GitHub attestations start with the first release after v7.17.0. Releases v7.7.0 through v7.17.0 have only the PyPI attestation, because the SLSA provenance upload was broken for them. Releases v.3.72.2 through v7.6.0 have the SLSA provenance and verify the same way.