lintoai/linto-platform-punctuationLinTO-platform-punctuation is a LinTO service for punctuation prediction. It predicts punctuation from raw text or raw transcription.
LinTO-platform-punctuation can either be used as a standalone punctuation service or deployed as a micro-service.
Prerequisites
Deploy
Usage
License
The punctuation service relies on a trained recasing and punctuation prediction model.
Some models trained on Common Crawl are available on recasepunc for the following the languages:
The punctuation service requires docker up and running.
For GPU capabilities, it is also needed to install nvidia-container-toolkit.
The punctuation only entry point in job mode are tasks posted on a REDIS message broker using Celery.
linto-platform-punctuation can be deployed two different ways:
1- First step is to build the image:
bashgit clone [***] cd linto-platform-punctuation docker build . -t linto-platform-punctuation:latest
or
bashdocker pull registry.linto.ai/lintoai/linto-platform-punctuation:latest
2- Download the models
Have the punctuation model ready at <MODEL_PATH>.
1- Fill the .env
bashcp .env_default .env
Fill the .env with your values.
Parameters:
| Variables | Description | Example |
|---|---|---|
| SERVICE_NAME | The service's name | my_punctuation_service |
| CONCURRENCY | Number of worker | > 1 |
2- Run with docker
bashdocker run --rm \ -v <MODEL_PATH>:/usr/src/app/model-store/model \ -p HOST_SERVING_PORT:80 \ --env-file .env \ linto-platform-punctuation:latest
Also add --gpus all as an option to enable GPU capabilities.
This will run a container providing an http API binded on the host HOST_SERVING_PORT port.
LinTO-platform-punctuation can be deployed as a microservice. Used this way, the container spawn celery workers waiting for punctuation tasks on a dedicated task queue. LinTO-platform-punctuation in task mode requires a configured REDIS broker.
You need a message broker up and running at MY_SERVICE_BROKER. Instance are typically deployed as services in a docker swarm using the docker compose command:
1- Fill the .env
bashcp .env_default .env
Fill the .env with your values.
Parameters:
| Variables | Description | Example |
|---|---|---|
| SERVICES_BROKER | Service broker uri | redis://my_redis_broker:6379 |
| BROKER_PASS | Service broker password (Leave empty if there is no password) | my_password |
| QUEUE_NAME | (Optionnal) overide the generated queue's name (See Queue name bellow) | my_queue |
| SERVICE_NAME | Service's name | punctuation-ml |
| LANGUAGE | Language code as a BCP-47 code | en-US or * or languages separated by "|" |
| MODEL_INFO | Human readable description of the model | "Bert based model for french punctuation prediction" |
| CONCURRENCY | Number of worker (1 worker = 1 cpu) | >1 |
Do not use spaces or character "_" for SERVICE_NAME or language.
2- Fill the docker-compose.yml
#docker-compose.yml
yamlversion: '3.7' services: punctuation-service: image: linto-platform-punctuation:latest volumes: - /my/path/to/models/punctuation.mar:/usr/src/app/model-store/model env_file: .env deploy: replicas: 1 networks: - your-net networks: your-net: external: true
3- Run with docker compose
bashdocker stack deploy --resolve-image always --compose-file docker-compose.yml your_stack
Queue name:
By default the service queue name is generated using SERVICE_NAME and LANGUAGE: punctuation_{LANGUAGE}_{SERVICE_NAME}.
The queue name can be overided using the QUEUE_NAME env variable.
Service discovery:
As a micro-service, the instance will register itself in the service registry for discovery. The service information are stored as a JSON object in redis's db0 under the id service:{HOST_NAME}.
The following information are registered:
json{ "service_name": $SERVICE_NAME, "host_name": $HOST_NAME, "service_type": "punctuation", "service_language": $LANGUAGE, "queue_name": $QUEUE_NAME, "version": "1.2.0", # This repository's version "info": "Punctuation model for french punctuation prediction", "last_alive": 65478213, "concurrency": 1 }
Returns the state of the API
Method: GET
Returns "1" if healthcheck passes.
Punctuation API
json{ "sentences": [ "this is sentence 1", "is that a second sentence", "yet an other sentence" ] }
Return the punctuated text as a json object structured as follows:
json{ "punctuated_sentences": [ "This is sentence 1", "Is that a second sentence ?", "Yet an other sentence" ] }
The /docs route offers a OpenAPI/swagger interface.
Punctuation-Worker accepts celery tasks with the following arguments:
text: Union[str, List[str]]
Returns a string or a list of string depending on the input parameter.
You can test you http API using curl:
bashcurl -X POST "[***]" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"sentences\": [ \"this is sentence 1\", \"is that a second sentence\", \"yet an other sentence\" ]}"
This project is developped under the AGPLv3 License (see LICENSE).
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务