Saravanan666/pypi-org huggingface dataset:
Package: renko
RenkoRenko chart creator.Example UsagefromrenkoimportRenko...# Create new renko instance. Give brick size and list of close prices as parametersrnk=Renko(1000,close)rnk.create_renko()print(rnk.bricks)...# The output will be like:[{'type':'first','open':10336.87,'close':10336.87}{'type':'up','open':10336.87,'close':11084.87}{'type':'up','open':11084.87,'close':11832.87}{'type':'up','open':11832.87,'close':12580.87}{'type':'up','open':12580.87,'close':13328.87}{'type':'up','open':13328.87,'close':14076.87}{'type':'up','open':14076.87,'close':14824.87}{'type':'up','open':14824.87,'close':15572.87}{'type':'up','open':15572.87,'close':16320.87,'low':14818.3}{'type':'up','open':16320.87,'close':17068.87}{'type':'up','open':17068.87,'close':17816.87}{'type':'up','open':17816.87,'close':18564.87}{'type':'up','open':18564.87,'close':19312.87,'low':17139.52}{'type':'up','open':19312.87,'close':20060.87,'low':18036.53}{'type':'up','open':20060.87,'close':20808.87}.........{'type':'up','open':48484.87,'close':49232.87}{'type':'up','open':49232.87,'close':49980.87}{'type':'up','open':49980.87,'close':50728.87}{'type':'down','open':49980.87,'close':49232.87,'high':50820.0}{'type':'down','open':49232.87,'close':48484.87}{'type':'down','open':48484.87,'close':47736.87}{'type':'down','open':47736.87,'close':46988.87}{'type':'down','open':46988.87,'close':46240.87}{'type':'down','open':46240.87,'close':45492.87,'high':47722.65}{'type':'down','open':45492.87,'close':44744.87}{'type':'down','open':44744.87,'close':43996.87}{'type':'down','open':43996.87,'close':43248.87}{'type':'down','open':43248.87,'close':42500.87}{'type':'down','open':42500.87,'close':41752.87}{'type':'up','open':42500.87,'close':43248.87,'low':41679.74}{'type':'down','open':42500.87,'close':41752.87}{'type':'down','open':41752.87,'close':41004.87}{'type':'down','open':41004.87,'close':40256.87}]fromrenkoimportRenko...# If you use it live in your strategies, pass the current price to check_new_price() function.# If new price change is big enough to create a new birck or bricks,# the bricks list will be updated accordingly.rnk=Renko(1000,close)rnk.create_renko()print(rnk.bricks)...rnk.check_new_price(100000)print("Bricks after new price added-------------")print(rnk.bricks)fromrenkoimportRenko...# You can plot the bricks as follows.rnk=Renko(1000,close)rnk.create_renko()rnk.draw_chart()...InstallationRun the following to install:pipinstallrenko
Package: renku-bio
renku-bioThis plugin extends Renku to easily annotate biological samples in Renku metadata. Samples can be annotated on either the project or dataset metadata (using --dataset).InstallationThe development version can be installed as a local Python package by running the following command from the root of the repo:pipinstall-e.The stable version is on PyPI and can be installed with pip:pipinstallrenku-bioUsageA CLI is available with entrypointrenku biothe gif belows demonstrates how to use it:[Click to expand]Full command from example above➜renkubioadd-sample\--description"Culture of liver cells from an adult mouse"\--age2\--taxon"Mus musculus"\--collector"SDSC"\--genderMalemouse_liver\--location"Lausanne"\--date2022-08-10After adding the biosample above, the project metadata graph would have the following structure:The new "BioSample" node was created byrenku bio add-sample. The information provided for sampling location, collector organization and taxon are enriched using third party APIs. For example, the "Taxon" node now has "scientificName", "taxonRank" and "parentTaxon" in addition to the name provided.[Click to expand]Compact view of the full biosample metadata[{"@id":"https://renkulab.io/projects/renku-bio/mouse_liver","@type":"http://bioschemas.org/BioSample","http://schema.org/dateCreated":"2022-08-10","http://bioschemas.org/collector":{"@id":"https://ror.org/02hdt9m26","@type":"http://schema.org/Organization","http://schema.org/name":"Swiss Data Science Center"},"http://bioschemas.org/isControl":false,"http://bioschemas.org/locationCreated":{"@id":"https://renkulab.io/projects/renku-bio/mouse_liver/loc","@type":"http://schema.org/Place","http://schema.org/latitude":46.5218269,"http://schema.org/longitude":6.6327025,"http://schema.org/name":"Lausanne, District de Lausanne, Vaud, Schweiz/Suisse/Svizzera/Svizra"},"http://bioschemas.org/samplingAge":2,"http://bioschemas.org/taxonomicRange":{"@id":"https://renkulab.io/projects/renku-bio/mouse_liver/tax","@type":"http://bioschemas.org/Taxon","http://bioschemas.org/parentTaxon":"Mus","http://bioschemas.org/scientificName":"Mus musculus","http://bioschemas.org/taxonRank":"species","http://schema.org/name":"house mouse"},"http://schema.org/description":"Culture of liver cells from an adult mouse","http://schema.org/gender":"Male","http://schema.org/name":"mouse_liver"}]Current state:Checklist:Interactively prompt user to select relevant API result (ROR, EBI, OSM)Use dataset annotations instead of projectUse Renku API to fetch metadata instead of CLI + subprocessChange console entrypoint to make into a renku pluginAdd support for experimental assay (potentially withLabProtocol)Restructure CLI into renku bio {sample,assay} {add,ls,rm,show}PoC to query a list of datasets (or projects) based on BioSample annotations.
Package: renku-r-tools
Renku-r-tools is a small python package that provides a CLI to setup R projects on Renku.Features:Replace the packrat-managed libraries of a R project by symbolic links. This is useful when relocating packrat libraries from the R project directory to the docker image.Replace the renv-managed libraries of a R project by symbolic links. This is useful when relocating renv libraries from the R project directory to the docker image.InstallationThe latest release is available on PyPI and can be installed usingpip:$ pip install renku-r-toolsIsolated environments usingpipxInstall and execute renku-r-tools in an isolated environment usingpipx.Install pipxand make sure that the$PATHis correctly configured.$ python3 -m pip install --user pipx
$ pipx ensurepathOncepipxis installed use following command to installrenku-r-tools.$ pipx install renku-r-tools
$ which renku-r-tools
~/.local/bin/renku-r-toolsUsageThe latest documentation is available onhttps://readthedocs.org.
Package: renku-sphinx-theme
A Sphinx theme for Renku documentation based on RTD theme.InstallationAddrenku-sphinx-themetosetup.pyorrequirements.txtused
for building your documentation.Sethtml_themeto'renku'indocs/conf.py.Configure at leastdescriptionandgithub_repoinhtml_theme_options.Enjoy your beautiful Renku documentation style.Style (css)This repo contains a scss file that generates a css file.
The css file shouldn’t be manually modified since it’s generated with the scss.
Instructions to change and run the scss file are inside the scss file.The easy way of doing style changes in this repository is to go to the renku repo, add a temporary css (custom.css)
in thedocs/conf.pyfile and follow this steps:https://renku.readthedocs.io/en/latest/developer/contributing/documentation.htmlThe reason for this is that renku docs is a better repository for testing changes.After doing the changes in the temporary css add this to custom.scss in this repository, build this into
a css file using the instructions and commit the css and scss files.BuildingTo build docs after doing changes, and test things inside this repositoryFrom the base folder…pip install-rdocs/requirements.txtThis should be done in case there where changes in fonts or new css files addedpip install--editable.There is no Makefile here but in order to do the “make html” action you should docd docssphinx-build-bhtml-d_build/doctrees . _build/htmlDocs will be built into_build/html...open this files with chrome to see the changes.ReleasingCreate a pull request updatingrenku_sphinx_theme/version.pyto the new version number
andCHANGES.rstto list the new changes.Once the pull request is merged,create a new release.The release will be automatically be pushed toPyPI.Changes0.3.0(2023-08-14)Big dependency update.0.2.3(2023-04-26)chore:add dependabot.yml
(76baee5)chore:remove dependency on non-existent compile-scss
(617e566)chore:fix pypi description
(23536d9)chore(deps):update sphinx-rtd-theme requirement
(2ca96ca)chore:bump python version
(0dd1fe6)chore:delete layout.html
(5fa988d)fix:update styles to fix sidebar background leaking into main content
(5ab737b)0.2.2(2021-07-09)design:new design for renku-sphinx
(3cf7ec7)chore:replace travis CI with github actions
(4056830)0.1.0(2018-05-17)Initial public release.
Package: renn
# Reverse Engineering Neural Networks (RENN)![build](https://github.com/google-research/reverse-engineering-neural-networks/workflows/build/badge.svg)rennis a collection of python utilities for reverse engineering neural networks. The goal of the package is to be a shared repository of code, notebooks, and ideas for how to crack open the black box of neural networks to understand what they are doing and how they work. Our focus is on research applications.Currently, the package focuses on understanding recurrent neural networks (RNNs). We provide code to build and train common RNN architectures, as well as code for understanding the dynamics of trained RNNs through dynamical systems analyses. The core tools for this involve finding and analyzing approximate fixed points of the dynamics of a trained RNN.All ofrennuses the [JAX](https://github.com/google/jax/) machine learning library for building neural networks and for automatic differentiation. We assume some basic familiarity with JAX in the documentation.See the [documentation](https://reverse-engineering-neural-networks.readthedocs.io/en/latest/) for more information.Authors:
- Niru Maheswaranathan (nirum@google.com)
- Vinay Ramasesh (ramasesh@google.com)
Package: reno
Reno is a release notes manager designed with high throughput in mind,
supporting fast distributed development teams without introducing
additional development processes.  Our goal is to encourage detailed
and accurate release notes for every release.Reno uses git to store its data, along side the code being
described. This means release notes can be written when the code
changes are fresh, so no details are forgotten. It also means that
release notes can go through the same review process used for managing
code and other documentation changes.Reno stores each release note in a separate file to enable a large
number of developers to work on multiple patches simultaneously, all
targeting the same branch, without worrying about merge
conflicts. This cuts down on the need to rebase or otherwise manually
resolve conflicts, and keeps a development team moving quickly.Reno also supports multiple branches, allowing release notes to be
back-ported from master to maintenance branches together with the
code for bug fixes.Reno organizes notes into logical groups based on whether they
describe new features, bug fixes, known issues, or other topics of
interest to the user. Contributors categorize individual notes as they
are added, and reno combines them before publishing.Notes can be styled using reStructuredText directives, and reno’s
Sphinx integration makes it easy to incorporate release notes into
automated documentation builds.Notes are automatically associated with the release version based on
the git tags applied to the repository, so it is not necessary to
track changes manually using a bug tracker or other tool, or to worry
that an important change will be missed when the release notes are
written by hand all at one time, just before a release.Modifications to notes are incorporated when the notes are shown in
their original location in the history. This feature makes it possible
to correct typos or otherwise fix a published release note after a
release is made, but have the new note content associated with the
original version number. Notes also can be deleted, eliminating them
from future documentation builds.Project Meta-dataFree software: Apache licenseDocumentation:https://docs.openstack.org/reno/latest/Source:https://opendev.org/openstack/reno/Bugs:https://storyboard.openstack.org/#!/project/933IRC: #openstack-release on OFTC
Package: renogymodbus
renogymodbusThis package is intended to help you communicate with a Renogy charge controller. It has been tested with a Renogy Rover Elite but should work with other Renogy devices.FeaturesRead real time dataAutomatic retriesConnecting to the charge controllerPlease check whether your charge controller has a rs232 or rs485 port.rs485Voucher code for 7% off Renogy:https://go.referralcandy.com/share/672HVC9rs485 to USB serial cable (UK)https://uk.renogy.com/rs485-to-usb-serial-cable/rs485 to USB serial cable (US)https://renogy.com/rs485-to-usb-serial-cable/rs232Unfortunately the rs232 to USB serial cable has been discontinued by Renogy. It is possible to make your own.Installing the packageTo install the package runpipinstallrenogymodbusThis package requires Python 3, depending on your setup you might have to instead run:pip3installrenogymodbusCommand line utilityTo run the command line utility and see the debug output run the following on the command line:renogymodbus--portname/dev/ttyUSB0--slaveaddress1usage:renogymodbus[-h][--portnamePORTNAME][--slaveaddressSLAVEADDRESS][--device{charge_controller,smart_battery}][--find-slave-address]optionalarguments:-h,--helpshowthishelpmessageandexit--portnamePORTNAMEPortnameforexample/dev/ttyUSB0--slaveaddressSLAVEADDRESSSlaveaddress1-247--device{charge_controller,smart_battery}Devicetoreaddatafrom.Eithercharge_controllerorsmart_battery--find-slave-addressFindslaveaddressofmodbusdeviceExample output for charge controllerRealTimeChargeControllerData
Solarvoltage:43.1V
Solarcurrent:0.09A
Solarpower:4W
Loadvoltage:0.0V
Loadcurrent:0.0A
Loadpower:0W
Batteryvoltage:13.9V
Batterystateofcharge:100%
Batterytemperature:-37°C
Controllertemperature:48°C
Maximumsolarpowertoday:51W
Minimumsolarpowertoday:0W
Maximumbatteryvoltagetoday:14.0V
Minimumbatteryvoltagetoday:13.1VExample output for smart batteryReal Time Smart Battery Data
Cell voltages: [3.3, 3.3, 3.3, 3.3, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]V
Cell temperatures: [24.0, 24.0, 24.0, 24.0, 1835.2, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]°C
BMS temperature: 0.0°C
Environment temperatures: [25.0, 25.0]°C
Heater temperatures: [25.0, 25.0]°C
Current: -0.2A
Voltage: 13.3V
Remaining capacity: 98.966Ah
Total capacity: 100.0Ah
State of charge: 98.966%
Cycle number: 0
Charge voltage limit: 14.8V
Discharge voltage limit: 10.0V
Charge current limit: 50.0A
Discharge current limit: -100.0APython usageTo use the library within your Python codeCharge ControllerfromrenogymodbusimportRenogyChargeControllercontroller=RenogyChargeController("/dev/ttyUSB0",1)controller.get_solar_voltage()Seehttps://github.com/rosswarren/renogymodbus/blob/main/renogymodbus/charge_controller.pyfor all available methodsSmart BatteryfromrenogymodbusimportRenogySmartBatterybattery=RenogySmartBattery("/dev/ttyUSB0",48)battery.get_voltage()Seehttps://github.com/rosswarren/renogymodbus/blob/main/renogymodbus/smart_battery.pyfor all available methods
Package: renoir
RenoirRenoir –/ˈrɛnwɑːr/– is a Python templating engine designed with simplicity in mind.In a nutshell{{ extend "layout.html" }}
{{ block title }}Members{{ end }}
{{ block content }}<ul>{{ for user in users: }}<li><ahref="{{ =user['url'] }}">{{ =user['name'] }}</a></li>{{ pass }}</ul>{{ end }}DocumentationThe documentation is available under thedocs folder.LicenseRenoir is released under the BSD License.
Package: renoir-haml
Renoir-HAMLRenoir-HAML is an extension for theRenoir engineproviding an HAML like syntax for templates. This is not a template engine but a compiler which converts HAML files to HTML Renoir templates.InstallationYou can install Renoir-HAML using pip:pip install renoir-hamlAnd add it to your Renoir engine:fromrenoir_hamlimportHamlrenoir.use_extension(Haml)Configurationparamdefaultdescriptionencodingutf8encoding for IOreloadFalseenable auto reload on file changesLicenseRenoir-HAML is released under BSD license. Check the LICENSE file for more details.
Package: renovation
RenovationOverviewThis is a drawing tool that produces floor plans needed to renovate an apartment.Walls, doors, windows, and dimension arrows are supported. Some other elements can be composed of them. For example, in the next section it is shown how to draw ventilation duct and French balcony.UsageTo install a stable version, run:pipinstallrenovationTo generate floor plans, run:python-mrenovation-c/path/to/config.ymlHere, config in YAML is a custom file where properties of each element to be drawn are set. These properties include location, orientation, size, and so on. Compared with drag-and-drop tools, config-based interface simplifies fine-grained control.Let us dive into details. Please look at ademo exampleas s reference while reading further explanations.The section namedprojectdefines properties of output such as:Extension (multi-page PDF document, directory with PNG images, or both)LocationDPI (dots-per-inch, resolution)In the demo config, only PNG output is requested and the generated images are shown below:In the section nameddefault_layout, below parameters are set for floor plans that do not override them in theirlayoutsections:Dimensions of area to be drawn (in real-world meters, i.e., meters prior to scaling)ScaleGrid settingsThe section namedreusable_elementsis designed to store arbitrary collections of elements that can be used by individual floor plans. Demo example uses it to define walls, windows, and doors.Finally, settings of individual floor plans are listed. These settings might include:TitleLayoutNames of element collections to reuseExtra elements
Package: renovosolutions.aws-cdk-aspects-security-group
cdk-aspects-library-security-groupA CDK library containing EC2 security group relatedCDK Aspectsand the ability to define custom aspects.FeaturesUtilize built in aspects for common cases:Disallow public access to any portDisallow public access to AWS Restricted Common ports (per the AWS Config rule)Disallow public access to SSH or RDP per CIS Benchmark guidelines and general good practiceDisallow public or ALL access to common management ports like SSH, RDP, WinRM, WinRM over HTTPSDisallow public or ALL access common relational DB ports like MSSQL, MySQL, PostgreSQL, and OracleDisallow public or ALL common web ports like HTTP (80, 8080) and HTTPS (443, 8443)Create any other aspect using the base security group aspect class.By default aspects generate errors in the CDK metadata which the deployment or synth process will find, but this can be changed with theannotationTypepropertyAll default provided aspects restrict based on the public access CIDRs (0.0.0.0/0and::/0) but you can also defined aspects with any set of restricted CIDRs or security group IDs you likeAPI DocSeeAPIExamplesTypescript// Add an existing aspect to your stack
Aspects.of(stack).add(new NoPublicIngressAspect());

// Add a custom aspect to your stack
Aspects.of(stack).add(new SecurityGroupAspectBase({
  annotationText: 'This is a custom message warning you how you should not do what you are doing.',
  annotationType: AnnotationType.WARNING,
  ports: [5985],
  restrictedCidrs: ['10.1.0.0/16'],
}));

// Change an existing aspects message and type
Aspects.of(stack).add(new NoPublicIngressAspect(
  annotationText: 'This is custom text.',
  annotationType: AnnotationType.WARNING
));
Package: renovosolutions.aws-cdk-aws-codeartifact
AWS::CodeArtifact Construct Library---All classes with theCfnprefix in this module (CFN Resources) are always stable and safe to use.The APIs of higher level constructs in this module are experimental and under active development.
They are subject to non-backward compatible changes or removal in any future version. These are
not subject to theSemantic Versioningmodel and breaking changes will be
announced in the release notes. This means that while you may use them, you may need to update
your source code when upgrading to a newer version of this package.AWS CodeArtifact is a fully managed artifact repository service that makes it easy for organizations of any size to securely store, publish, and share software packages used in their software development process. CodeArtifact can be configured to automatically fetch software packages and dependencies from public artifact repositories so developers have access to the latest versions. CodeArtifact works with commonly used package managers and build tools like Maven, Gradle, npm, yarn, twine, pip, and NuGet making it easy to integrate into existing development workflows.For further information on AWS CodeArtifact, see theAWS CodeArtifact documentation.Add a CodeArtifact Domain to your stack:import*ascodeartifactfrom'@renovosolutions/cdk-library-aws-codeartifact';newcodeartifact.Domain(stack,'domain',{name:'example-domain'});Add a CodeArtifact Repository to your stack:import*ascodeartifactfrom'@renovosolutions/cdk-library-aws-codeartifact';constdomain=newcodeartifact.Domain(stack,'domain',{name:'example-domain'});constrepository=newcodeartifact.Repository(stack,'repository',{name:'repository',domain,});It is also possible to use theaddRepositorymethod oncodeartifact.Domainto add a repository.import*ascodeartifactfrom'@renovosolutions/cdk-library-aws-codeartifact';constdomain=newcodeartifact.Domain(stack,'domain',{name:'example-domain'});domain.addRepository('repo',{name:'repository'});
Package: renovosolutions.aws-cdk-aws-sso
CDK Library for AWS SSONote: This construct library is currently being developed and requires more tests, but fundamentally it should work.This CDK library provides L2 constructs for the AWS SSO CfnPermissionSet and CfnAssignment. Assignment is not consumed by other resources so it's attributes and properties are minimal, but a L2 construct makes it easier to interact with and allows providing a more fully featured construct for the Permission Set and assignment requires.FeaturesL2 Construct forPermissionSetincluding importing from ARN and granting the permissionL2 Construct forAssignmentSome enums to provide valid inputs for certain propertiesAPI DocSeeAPIExamplesPermissionSetimport{PermissionSet,Assignment,PrincipalTypes}from'@renovosolutions/cdk-library-aws-sso';import{App,Stack,StackProps,aws_ssoassso,aws_iamasiam,Duration,}from'aws-cdk-lib';//createapermissionsetconstpermissionSetExample=newPermissionSet(this,'permissionSet',{ssoInstanceArn:'arn:aws:sso:::instance/ssoins-1234567891234567',name:'ExamplePermissionSet',description:'Example permission set with some policies',awsManagedPolicies:[iam.ManagedPolicy.fromAwsManagedPolicyName('job-function/ViewOnlyAccess'),],customerManagedPolicyReferences:[{name:'someServiceLogRead',//mustexistinthetargetaccountpath:'/',}],relayStateType:'https://us-east-1.console.aws.amazon.com/cloudwatch/home'})//assignittoanaccount/principalwithanAssignmentnewAssignment(this,'ExampleAssignment',{permissionSet:permissionSetExample,principal:{principalId:'25750630-0ae9-479a-97c2-0afc2d5b4eac,principalType:PrincipalTypes.GROUP,},targetId:'124567890123456',});//assignittosomethingelsewithagrantpermissionSetExample.grant('permissionSetExampleAssignment',{principal:{principalId:'12350630-0ae9-479a-97c2-0afc2d5b4eac',principalType:PrincipalTypes.GROUP,},targetId:'344567890123456',});//importanexistingpermissionsetconstexistingPermissionSetExample=PermissionSet.fromPermissionSetArn(this,'existingPermissionSetExample','arn:aws:sso:::permissionSet/ssoins-1234567891234567/ps-55a5555a5a55ab55');
Package: renovosolutions.aws-cdk-control-tower-lifecycle-events
cdk-library-control-tower-lifecycle-eventsNOTE: This project is in active development.This construct library contains events that represent lifecycle events in Control Tower or events related to actions in Control Tower. See theAPIfor full details on the available constructs.ReferencesReferencefor creating constructs that extend and existing one more easilyControl Tower Lifecycle EventsAWS doc