Saravanan666/pypi-org huggingface dataset:
Package: commonroad-dataset-converter
Dataset ConvertersThis repository contains converters from different datasets to CommonRoad scenarios using a common commandline interface.
Currently, we support:highD,inD,INTERACTION,exiD,rounD,MONA,SIND.Installpipinstallcommonroad-dataset-converterInstall with support for nuplan datasetpipinstallcommonroad-dataset-converter[nuplan]Development setupThis project usespoetry. Please follow the instructions to create the virtual development environment.UsageType following command for help$crconvert--help
Usage:crconvert[OPTIONS]INPUT_DIROUTPUT_DIRCOMMAND[ARGS]...GeneratesCommonRoadscenariosfromdifferentdatasets

Arguments:INPUT_DIRPathtothedatafolder[required]OUTPUT_DIRDirectorytostoregeneratedCommonRoadfiles[required]Options:--num-time-stepsINTEGERMaximumnumberoftimestepsintheCommonRoadscenario[default:150]--num-planning-problemsINTEGERNumberofplanningproblemsperCommonRoadscenario.Morethanonecreatesacooperativescenario.[default:1]--keep-ego/--no-keep-egoVehiclesusedforplanningproblemshouldbekeptinthescenario.[default:no-keep-ego]--obstacles-start-at-zero/--no-obstacles-start-at-zeroThelowesttimestepinthescenarioissettozero.[default:no-obstacles-start-at-zero]--downsampleINTEGERDecreasedtbyn*dt[default:1]--num-processesINTEGERNumberofprocessestoconvertdataset.[default:1]--all-vehicles/--no-all-vehiclesCreateoneplanningproblem/scenarioforeachvalidvehicle.Invalidatesnum-time-steps.[default:no-all-vehicles]--routability-check[nocheck|strict]Checkroutabilityofplanning_problem[default:RoutabilityCheck.Strict]--output-type[xml|pb]FiletypeofCommonRoadscenarios[default:xml]--max-scenariosINTEGEROnlycreateuptonscenarios.--samples-per-recordingINTEGERRandomlysamplenscenariosfromeachrecording.--helpShowthismessageandexit.

Commands:exidConverttheexiDdatasetintoCommonRoadscenario(s).highdConvertthehighDdatasetintoCommonRoadscenario(s).indConverttheinDdatasetintoCommonRoadscenario(s).interactionConverttheINTERACTIONdatasetintoCommonRoadscenario(s).monaConverttheMONAdatasetintoCommonRoadscenario(s).roundConverttherounDdatasetintoCommonRoadscenario(s).sindConverttheSINDintoCommonRoadscenario(s).DockerThe dataset converter can also be used within a docker container. We provide aDockerfileto build the image.dockerbuild-tcommonroad-dataset-converter.The image's entrypoint callscrconvert. Any arguments passed todocker runare passed to the executable. To access the original dataset and converted scenarios, provide it as a volume mount-v PATH_TO_DATASET:/data:roand-v PATH_TO_OUTPUT_DIRECTORY:/outputExample: Convert the highD datasetdockerrun-v`pwd`/highd_dataset:/data:ro-v`pwd`/highd_scenarios:/outputcommonroad-dataset-converter\--max-scenarios20--samples-per-recording20/data/outputhighd
Package: commonroad-helper-functions
CommonRoad Helper FunctionsInstallation as packageInstall this package with the following command:pip install commonroad-helper-functionsCommonRoad ScenariosIn order to test the provided functions, download the scenarios by cloning the commonroad-scenarios repository:git clone https://gitlab.lrz.de/tum-cps/commonroad-scenarios.gitMake sure to place the folder on the same directory level as this repository:|
|-- commonroad_helper_functions (This repository)
|-- commonroad_scenarios
|FunctionalitiesSensor Occlusion ModelAs part of this repository a sensor model is implemented. Based on the position of an ego vehicle, the visible area is determined and all dynamic objects within this area are returned. Occlusions by dynamic objects can be taken into account, as well as by the road geometry.
The two examples show the visible area in green. In contrast to the left, the right video uses a wall buffer of 5m. This means that we assume a buffer of 5m around the lane geometry that can be seen through.A dynamic objects is considered as visible as soon as any part of it can be physically seen from the ego position.DeploymentImport sensor model functionfrom commonroad_helper_functions.sensor_model import get_visible_objectsCall functionvisible_object_ids, visible_area = get_visible_objects(scenario, time_step, ego_pos)Optional Argumentssensor_radius: Float number that defines the sensor radius in meterocclusion: True if occlusions by dynamic objects should be consideredwall_buffer: Float number that defines the wall buffer in meter (see example above)
Package: commonroad-openscenario-converter
CommonROAD-OpenSCENARIO ConverterAutomatic Traffic Scenario Conversion betweenOpenSCENARIOandCommonRoad. Currently, only the conversion fromOpenSCENARIO toCommonROAD (osc2cr) is developed.Using the ConverterThe recommended way of installation if you only want to use the OpenSCENARIO-CommonROAD Converter
(i.e., you do not want to work with the code directly) is to use the PyPI package:pipinstallcommonroad-openscenario-converterDevelopmentFor developing purposes, we recommend usingAnacondato manage your environment so that
even if you mess something up, you can always have a safe and clean restart.
A guide for managing python environments with Anaconda can be foundhere.First, clone the repository.After installing Anaconda, create a new environment with (>=3.9) and enter it:$condacreate-ncommonroad-py39python=3.9-y
$condaactivatecommonroad-py39
or
$sourceactivatecommonroad-py39Then, install the dependencies with:$cd<path-to-this-repo>
$pipinstall.
$condadevelop.To test the installition, run unittest:$cdtests
$python-munittest-vOpen Simulation Interface (OSI) and UDP DriverIf you want to use theesminiUDPDriverController in combination with OSI for including
external driver models or vehicle simulators, you need to install OSI manually,
seehere.Contributors (in alphabetical order by last name)Yuanfei LinMichael RatzelDocumentationThe documentation of our toolbox is available on our website:https://cps.pages.gitlab.lrz.de/commonroad-openscenario-converter/.In order to generate the documentation via Sphinx locally, run the following commands in the root directory:$pipinstall-r./docs/requirements_doc.txt
$cddocs/sphinx
$makehtmlThe documentation can then be launched by browsing./docs/sphinx/build/html/index.html/.AcknowledgmentsWe would like to extend our heartfelt gratitude to the team behindesminifor
their remarkable effort in developing the simulation tool. Specifically, we would like to express our sincere
appreciation toEmil Knabefor his invaluable contribution in reviewing and accepting the proposed changes to the esmini interface,
and toSebastian Maierhoferfor maintaining the converter from OpenDRIVE to lanelets.
We gratefully acknowledge partial financial support by the German Federal Ministry for Digital and Transport (BMDV)
within the projectCooperative Autonomous Driving with Safety Guarantees(KoSi).CitationIf you usecommonroad-openscenario-converterfor academic work, we highly encourage you to cite ourpaper:@inproceedings{Lin2023Osc2Cr,
	author = {Yuanfei Lin, Michael Ratzel, and Matthias Althoff},
	title = {Automatic Traffic Scenario Conversion from {OpenSCENARIO} to {CommonRoad}},
	booktitle = {Proc. of the IEEE Int. Conf. on Intell. Transp. Syst.},
	year = {2023},
	pages= {},
}If you use this project's code in industry, we'd love to hear from you as well;
feel free to reach out toYuanfei Lindirectly.
Package: commonroad-reactive-planner
Reactive PlannerThis project generates solutions to trajectory planning problems given in theCommonRoadscenario format.
The trajectories are generated using the sampling-based approach in [1][2]. This approach plans motions by sampling a
discrete set of trajectories, represented as quintic polynomials in a Frenet frame and selecting an optimal trajectory according
to a given cost function.Getting StartedThese instructions should help you to install the trajectory planner and use it for development and testing purposes.To install the trajectory planner from PyPi, please run:pipinstallcommonroad-reactive-plannerRequirementsThe software is  developed and tested on recent versions of Linux. The required python dependencies are listed inrequirements.txt.For the python installation, we suggest the usage ofAnaconda.For the development IDE we suggestPyCharmInstallation from SourceClone this repository & create a new conda environment, e.g.,conda create -n commonroad-py37 python=3.7Install the package:Install the package via pip:pip install .Orinstall the dependencies withpip install -r requirements.txtand add the root folder to the python path of your interpreterHow to runMain example scriptrun_planner.py: The example script shows how to run the planner on an exemplary
CommonRoad scenario. Therein, the following steps are included:creating a planner configurationinstantiating the reactive plannerrunning the planner in planning cycles with a fixed re-planning frequencyLiterature[1] Werling M., et al.Optimal trajectory generation for dynamic street scenarios in a frenet frame. In: IEEE International Conference on Robotics and Automation, Anchorage, Alaska, 987–993.[2] Werling M., et al.Optimal trajectories for time-critical street scenarios using discretized terminal manifoldsIn:
The International Journal of Robotics Research, 2012
Package: commonroad-route-planner
CommonRoad Route PlannerThe basic functionality of this package is to find sequences of lanelets (also referred to as routes) that lead from the initial lanelet(s)  to the goal lanelet(s) of a given planning problem. It also works with survival scenarios (where no goal region is specified). In addition, the package generates a reference path for each of the planned route, which can be used to construct a curvilinear coordinate system at a later stage.Supported BackendsThe planner supports different backends to search for the shortest route in the scenario:NETWORKX: uses built-in functions from the networkx package, tends to change lanes laterNETWORKX_REVERSED: uses built-in functions from the networkx package, tends to change lanes earlierPRIORITY_QUEUE: uses A-star search to find routes, lane change maneuver depends on the heuristic costInstallationTo use this module, run the setup script in the root folder:pipinstall.Or simply install the dependencies listed inrequirements.txtand add this repository to your python path.Minimal ExampleA tutorial notebook and an example script can be found under thetutorial/folder.
Package: commonroad-vehicle-models
Python Vehicle Models of CommonRoadThis package contains all vehicle models of theCommonRoad benchmarks.We provide implementations of the vehicle dynamics, routines to convert initial states, and vehicle parameters.DocumentationFor a detailed explanation of the vehicle models, please have a look at thedocumentation.InstallationTo use vehicle models and parameters, runpip install commonroad-vehicle-modelsCode examplesFor an extended simulation example demonstrating the advantages of more complicated models, we refer to ourgitlab repository. A simple simulation example for using the single-track model in combination with an odeint solver would befromscipy.integrateimportodeintimportnumpyfromvehiclemodels.init_ksimportinit_ksfromvehiclemodels.parameters_vehicle1importparameters_vehicle1fromvehiclemodels.vehicle_dynamics_ksimportvehicle_dynamics_ksdeffunc_KS(x,t,u,p):f=vehicle_dynamics_ks(x,u,p)returnftStart=0# start timetFinal=1# start time# load vehicle parametersp=parameters_vehicle1()# initial state for simulationdelta0=0vel0=15Psi0=0sy0=0initialState=[0,sy0,delta0,vel0,Psi0]x0_KS=init_ks(initialState)t=numpy.arange(0,tFinal,0.01)u=[0,5]x=odeint(func_KS,x0_KS,t,args=(u,p))ContributeIf you want to contribute new vehicle models, you can create a merge request in ourrepository, or contact via ourforum.ChangelogCompared to version 2.0.0 the following features were added/changed:linearized kinematic single-track model added as an additional vehicle modelvehicle parameters are stored in YAML-filesparameter configuration of vehicles are generated from YAML-files usingOmegaConf(backwards compatible)ReferencingIf you use CommonRoad for your research, please citeour paper:@inproceedings{Althoff2017a,
	author = {Althoff, Matthias and Koschi, Markus and Manzinger, Stefanie},
	title = {CommonRoad: Composable benchmarks for motion planning on roads},
	booktitle = {Proc. of the IEEE Intelligent Vehicles Symposium},
	year = {2017},
}
Package: common-robotics-utilities
common_robotics_utilitiesCommon utility functions and algorithms for robotics work used by ARC & ARM labs and TRI.BindingsBinding codes copied frommpetersen94/drake:gcs2with:adaption to latest commit of the cpp librarywrite tests in a more pythonic waymore testsInstallationRequirements:cmake, Eigen3(Pip) scikit-build, calver, numpy
Note that onlyEigen3is required for building the C++ library, whilescikit-buildis required, other dependencies are automatically resolved by python's build system.pipinstall.UsageThe C++ library supports parallelism using OpenMP in finding nearest k neighborhoods, connecting roadmaps, etc.
However, cares must be taken when calling these codes.
In general, if python codes is being executed in the parallel region with parallelism activated: single thread performance or deadlock will be observed.
One should either:(best performance) write most planning problem related codes in C++, for an example, seeGraphPuzzle.(avoid deadlock) turn-off parallelism by passinguse_parallel=Falsein those function.C++ libraryBuildingmkdirbuild&&cdbuild
cmake..cmake--build.
cmake--install.Testingmkdirbuild&&cdbuild
cmake..ctestpytestbindings/test
Package: commonsApi
API Testing CommonsThis is a package to automate apis in a simple way by using common reusable functions.This module containes the major reusable functions which can be imported and accessed directly which will reduce the time and code redundancy.Installationpip install commonsApiMethods availableget_api(endpoint, header)post_api(endpoint, request_payload, header)put_api(endpoint, request_payload, header)delete_api(endpoint, data, header)patch_api(endpoint, request_payload, header)validate_status_code(response, expected_status)validate_schema(response, expected_schema)validate_strings(actual_message, expected_message)value_present(response, expected_value)is_json(response)Sample codeimportcommonsApiurl="https://api.postcodes.io/random/postcodes"header={}resp=commonsApi.get_api(url,header)print(resp.json())Raise if any issues/changes neededPlease raise an issuehereif anything
Package: common-tags
common-tagsCommon templatetags provides for Django.InstallationCommon Tags is available directly fromPyPI:Installing the package.$ pip install common-tagsDon’t forget to add'common'to your'INSTALLED_APPS'setting(without migrations).# settings.py
INSTALLED_APPS = [
    ....
    'common',
]Usage in template{% load common_tags %}For complete usage, seecommon/templatetags/common_tags.pyContributingFeel free toopen a bugorcontribute to code!
Package: common_toolkit
Common Toolkit通用的python工具包1、说明common_toolkit包含以下几部分功能，可按需加载不同功能包的依赖模块（参考3）cli: ,安装本包会同时扩展一些shell命令，详细介绍如下py说明：在当前目录创建python项目骨架相关命令使用：$py --helpdevelopment: 常见python开发相关的工具包penetration: 渗透测试相关功能包2、安装pipinstallcommon_toolkit3、依赖按需加载eg1: 只想要使用开发相关的依赖pipinstall"common_toolkit[development]"eg2: 只想要使用渗透测试相关的依赖pipinstall"common_toolkit[penetration]"eg3: 如果需要使用两个及以上相关的依赖，请在中括号中用,将需要安装的依赖包名分隔pipinstall"common_toolkit[development,penetration]"
Package: common-tracker
Not On PyPiThis is a reserved package name to preventdependency confusion / substitution attack. If installed, will immediately raise an error indicating that the wrong PyPi repository was used.If someone would like to use this package name, I would be happy to discuss handoff. Please contact me through a Github issue onKyleKing/not-on-pypior if I don't respond, you can try mygmailaccountdev.act.kyle
Package: common-util-py
common-util-pycommon utilities in pythonhow to install$python3-mvenvpy312_env
$sourcepy312_env/bin/activate
$virtualenv--python=/usr/bin/python3py39_env
$sourceenv_py39/bin/activate
$pipinstall.
$# or$python3.8-mvenvenv_py38
$sourceenv_py38/bin/activate
$pipinstall.how to build$pythonsetup.py--help-commands
$pythonsetup.pysdisthow to test$pythonsetup.pytest$pythonsetup.pynosetestsread moreherehttps://www.codingforentrepreneurs.com/blog/pipenv-virtual-environments-for-python/https://packaging.python.org/https://betterscientificsoftware.github.io/python-for-hpc/tutorials/python-pypi-packaging/how to upload to pypi$pythonsetup.pysdist
$pipinstalltwinecommands to upload to the pypi test repository$twineupload--repository-urlhttps://test.pypi.org/legacy/dist/*or$twineupload--config-file~/.pypirc-rtestpypidist/common_util_py-0.0.1.tar.gztest install$pipinstall--index-urlhttps://test.pypi.org/simple/common-util-py
$# or local install for quick test$pipinstalldist/common_util_py-<version>.tar.gztested install via pypi on the following py versionpythontested installed3.9yes3.10yes3.11yes3.12yescommand to upload to the pypi repository$twineuploaddist/*
$pipinstallcommon-util-py
Package: commonutilslib
A library with some common utility methods for python like tempdir and PushdDocumentation:https://common-utils.readthedocs.io/en/latest/usage.htmlDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesPlease refer to USAGE.rstHistory0.0.1 (26-02-2019)First code creation0.1.0 (26-02-2019)First official release0.1.1 (18-10-2019)Update template and bumped dependencies.0.1.2 (18-10-2019)Bumped dependencies0.1.3 (26-04-2021)Bumped dependencies.0.1.4 (08-06-2021)Bumped dependencies.
Package: common-utils-py
Nevermined Python common utilsProvides common functions to interact with Nevermined ecosystemMain componentsDID and DDODID format: 'did:nv:<32bytes-hex-representation>DID is the universal identifier for assets in the Nevermined networkDDO is the json document thatDID resolverGiven a valid did, returns the associated DDO document which define
the asset metadata and other services offered for the assetMetadataService AgreementsAttributionThis project is based in theOcean Protocol Common-utils-py. It keeps the same Apache v2 License and adds some improvements.LicenseCopyright 2020 Keyko GmbH.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Package: common-version
# common_version基于包管理器以及漏洞网站的版本表达式统一化. code-block:: bashgit clonehttps://github.com/hsc1102/common_version.gitcd common_version
pip install “flake8<3.8” bumpversion pep8-naming
flake8 –install-hook git
git config –bool flake8.strict true版本发布. code-block:: bashbumpversion patch
git push origin master –tags
git pull && bumpversion patch && git push origin master –tags. code-block:: bashpip install twine whell
python setup.py sdist bdist_wheel
twine upload dist/*
Package: common-web
#Common Package
This is a common package for base, my web project base package (With Django).DtoResObj (this is Response Dto format:{"code":200, "message":"", data: None})Middlewaresexception_middleware (this is gobal exception middleware for Django)Exception (this is custom exception)AuthExceptionBusinessExceptionUtilsdate_utilget_time_by_str(date_str, date_format=DATE_TIME_FORMAT)convert_date_str_format(date_str, old_format, new_format)get_date_str_by_time(date_format, timestamp)file_utilread_files_in_folder(file_path)write_json_to_file(file_path, data, encoding='UTF-8')http_utilget(url, params=None, headers=None)get_json(url, params=None, headers=None)post(url, params=None, headers=None, timeout=30)post_json(url, params=None, headers=None, timeout=30)festival_utilget_holiday_date_by_year_name(year, festival_name)get_holiday_by_date(date_str)is_holiday(date_str)
Package: commonz
There is already many python modules,But i think some are wrong, and should not be used,or they have a lot of confusing options.Thats the reason for me to write modules wrapping what i need.Then instead of looking again and again what should i use and how to use it correctly, i just go into my own modules.Also making these modules independent of projects allows to share the upgrades and bug fix more easily.📝 NoteThe modules are written for Python3 and no effort are made for compatibility with Python2.The modules are only tested on Linux O.S.  hoping to be able to work on other platforms.📜 HistoryOrigin:Initiate byN-z0in 2017❤️ Special thanksI am very grateful for all those modules that i use in my own modules,of course i respect their license, and would like to push these people on top,Because without them im not much.