Saravanan666/pypi-org huggingface dataset:
Package: isosplit6
isosplit6Isosplit is a non-parametric clustering method that does not require adjustable parameters nor parametric assumptions about the underlying cluster distributions. The only assumption is that clusters are unimodal and separated from one another by hyperplanes of relatively low density. The technique uses a variant of Hartigan's dip statistic and isotonic regression in its kernel operation.Motivation: Many clustering algorithms require the tuning of parameters for each application or dataset, making them unsuitable for automated procedures that involve clustering. Some techniques require an initial estimate of the number of clusters, while density-based techniques typically require a scale parameter. Other parametric methods, such as mixture modeling, make assumptions about the underlying cluster distributions.Isosplit is used by theMountainSortspike sorting algorithm.preprintInstallation and usagepipinstallisosplit6fromisosplit6importisosplit6# Prepare a N x M Numpy Array# N = number of observations# M = number of featuresfeatures=...cluster_labels=isosplit6(features)
Package: isostatic
IsostaticA repository for designing isostatic structuresDescripciónUn repositorio para diseño de estructuras isostaticas mediante un paquete de python.LicenciaVea el archivo licencia engithubModulosPoint (2D)Support (vertical, horizontal, momentos)rotations (Solo casos de carga lineal)InstalacionpipinstallisostaticUna vez instalado importe los modulosfromisostaticimportPoint,Support,LinealLoad,GeneralLoadLineal
Package: isostream
isostreamIsoStream Python ClientA simple wrapper around the ISOStream API that produces JSON or well formated pandas DataFrames from query results.
The the API client, methods, inputs and responses and all dynamically created from the OpenAPI specification of the IsoStream REST API.InstallationYou can install the library with:pip install isostreamQuickstartThe ISOStream client is dynamically generated from the OpenAPI specification from the ISOStream API.
See theISOStream API Documentationfor more details.
All of the REST API endpoints available on client as methods.from isostream import IsoStream

client = IsoStream("<your_api_key>")

df = client.dalmp_node(node="WESTERN HUB", start="2021-01-01", end="2021-02-01", iso="PJM")All string timestamps can also be provided as datetime objects.To see a list of available API methods:client.api_methods()

# or filter by a specific keyword to see only relevant methods:
client.api_methods(filter="dalmp")By default, the client returns all queries in appropriated typed and logically pivoted pandas DataFrames.
You can alter this behavior with the 'as_df' and 'pivot' flags:raw = client.meta_nodes(iso="PJM", as_df=False)
Package: isosurfaces
IsosurfacesConstruct isolines/isosurfaces of a 2D/3D scalar field defined by a function, i.e. curves over whichf(x,y)=0or surfaces over whichf(x,y,z)=0. Most similar libraries use marching squares or similar over a uniform grid, but this uses a quadtree to avoid wasting time sampling many far from the implicit surface.This library is based on the approach described inManson, Josiah, and Scott Schaefer. "Isosurfaces over simplicial partitions of multiresolution grids." Computer Graphics Forum. Vol. 29. No. 2. Oxford, UK: Blackwell Publishing Ltd, 2010.An example graph, including quad lines, ofy(x-y)^2 = 4x+8(Python expression:y*(x-y)**2 - 4*x - 8)Installationpip3installisosurfacesUsagefromisosurfacesimportplot_isolineimportnumpyasnpdeff(x,y):returny*(x-y)**2-4*x-8curves=plot_isoline(lambdau:f(u[0],u[1]),np.array([-8,-6]),np.array([8,6]),# Increasing min_depth can help if you have small featuresmin_depth=3,# Ensure max_quads is more than 4**min_depth to capture details better# than a 2**min_depth by 2**min_depth uniform gridmax_quads=1000,)forcurveincurves:print(', '.join(f"({p[0]:.3f},{p[1]:.3f})"forpincurve))Dev examplespython3isoline_demo.py&&xdg-openout/demo.svg
manim-pqlisosurface_demo.py--renderer=opengl--enable_guiPyflakes, allowing manim star importspython3-mpyflakes.|grep-v"star imports: manim"Build source archive and wheel:rm-rfdistbuildisosurfaces.egg-info
python3setup.pysdistbdist_wheel
twinecheckdist/*# for test:twineupload--repository-urlhttps://test.pypi.org/legacy/dist/*# for actualtwineuploaddist/*Code formattingisosurfacesusesblackandisort. A Github Action will run to make sure it was applied.RelatedRelated projects:(2D, grid-based)https://pypi.org/project/meander/(2D, grid-based)https://pypi.org/project/contours/(Archived)https://github.com/AaronWatters/contouristOther terms for an isoline:ContourLevel curveTopographic map
Package: isotel-idm
ISOTEL Data-acquisition & Metering Project offers a complete solution for wired and wireless communication with sensor & control devices. IDM Project strives for correct presentation of sensor measurements, accuracy, precision and easy description of their complex transfer functions to fulfil requirements of accurate metering and precise control in control systems.
Package provides API to IDM Smart Gateway and  in addition hardware specific support for: Monodaq-U-X, and Energy Control Modules.
Package: isotel-iot
IoT library is an API interface to communicate with an ISOTEL of Things (IoT) server.
An IoT server provides innovative ways to interact with hardware devices like sensors, actuators connected via serial links, USB, bluetooth, wireless, etc., in a distributed, profile-less manner, to support heterogeneity and scalability.
isotel-iot API can bind to an IoT server, search for available devices, as well as interact with them by retrieving and modifying their values.
IoT servers can connect to each others via Skype, a feature extremely useful to reach out to remote devices behind firewalls.
Package: isotoma.buildout.basicauth
This buildout extension allows your buildouts to use${buildout:extends}or
eggs that are protected by basic auth. The minimum configuration:[buildout]
extensions = isotoma.buildout.basicauthAny downloads that require basic auth will now prompt for a username and
password. It will be stored in a secure keyring if one is available. If your
credentials are in .pypirc they will be detected and used.You can provide credentials to the extension via builout, for non-interactive
situations. For example:[basicauth]
credentials =
    github
interactive = no

[github]
uri = https://raw.github.com/
username = user
password = chunkyEach of the credentials parts provides authentication details for a different
uri. The part must contain a uri, user and password to be used by the
extension.The “interactive” option determines whether or not fetcher methods can prompt
the user for input.Changelog0.0.7 (2013-07-30)Read basicauth:credentials option from ~/.pypirc.0.0.6 (2013-04-18)Remove the hard-dependency on python-keyring0.0.5 (2012-09-14)Support usernames and passwords with ‘/’ in them.0.0.4 (2012-07-28)Restore pytho2.4 support.0.0.3 (2012-07-28)Force download to happen straight away so we can handle retries for buildout.0.0.2 (2012-07-28)Fix injection of credentials in urlretrieve0.0.1 (2012-07-27)Disable keyring backend until we can support it on python2.40.0.0 (2012-07-27)Initial release
Package: isotoma.buildout.logger
This package provides abuildoutextension for logging buildout (and any child
processes). When added to your buildout extensions, it is on. By default, it logs
to parts/log/ but this can be overridden in your buildout.cfg.This recipe uses the ‘tee’ unix command.Logging your buildout runYou just need to add an extension to your buildout.cfg. Optionally, you can set where the log must be written:[buildout]
extensions = isotoma.buildout.logger
buildout-log = /var/log/buildout.logOptional Parametersbuildout-logPath to a file to log to. By default this is a unique name assigned at runtime in parts/log/.snapshot-srcA file to take a copy of every time everytime buildout runs. Default: ./buildout.cfgsnapshot-dstWhere to copy snapshot-dst to. Defaults to same folder as buildout-log.RepositoryThis software is available from ourrecipe repositoryon github.LicenseCopyright 2010 Isotoma LimitedLicensed 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 athttp://www.apache.org/licenses/LICENSE-2.0Unless 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: isotoma.recipe.buildbot
IntroductionThis package provides 2 recipes for helping you manage your buildbot master and slave.
We purposefully do not provide machinery for generating project configuration.Creating and managing your masterTo create a buildbot master, add something like this to your buildout.cfg:[buildbot]
recipe = isotoma.recipe.buildbot
cfgfile = path/to/master.cfg
config =
    "PORT_WEB": "8080",cfgfile is a normal buildbot master config, but it has a config object in its global namespace
that contains the buildout managed properties set under config.This recipe will also create a wrapper for starting, stopping, reconfiguring and
checking the configuration of the master. It will be in your buildout’s bin directory and have
the same name as your part.For buildbot 0.8.0+ installations, the recipe will create and perform migrations on your database.Mandatory ParameterscfgfilePath to a buildbot configuration file. BuildMasterConfig will already be defined, so dont redeclare it.configA list of buildout managed settings that are passed to the buildbot master configurationOptional ParameterseggsAny eggs that are needed for the buildbot to function. These are eggs to support your buildbot, as opposed to eggs to support the code buildbot is running for you.dburlA buildbot DBSpec for connecting to your buildbot database. Default is sqlite in var directory. See buildbot manual for help setting this.Creating slavesTo create a buildbot master, add something like this to your buildout cfg:[bb-slave-1]
recipe = isotoma.recipe.buildbot:slave
basedir = ${buildout:directory}/bb-slave-1
master-host = 10.0.2.2
master-port = 8082
username = blah
password = blahThis will add a slave to the bb-slave-1 directory and add a bb-slave-1 start/stop script to the bin directory.Mandatory ParametersbasedirWhere the slave will be created and where it stores its temporary datamaster-hostThe IP or hostname that a slave should connect tomaster-portThe port the slave should connect tousernameA valid slave username on the master server to connect withpasswordA valid slave password on the master server to connect withChangelog0.0.33 (2012-06-11)And of course, brown paper bag0.0.32 (2012-06-11)SIGUSR1 will become “graceful shutdown”, so use SIGUSR2 for log rotationAdd logrotate and graceful-shutdown helpers to wrapper script0.0.31 (2012-06-06)Nothing changed yet.0.0.30 (2012-05-21)Nothing changed yet.0.0.29 (2012-05-07)Support buildbot 0.8.7 (pre)0.0.28 (2012-04-12)Support buildbot 0.8.60.0.27 (2011-10-04)Fix slave umask after twistd clobbers it
Package: isotoma.recipe.cluster
Cluster buildout recipeThis package providesbuildoutrecipes for creating start/stop scriptsMandatory ParametersservicesA list of services to start and stopOptional ParametersThere are no optional parameters.RepositoryThis software is available from ourrecipe repositoryon github.LicenseCopyright 2010 Isotoma LimitedLicensed 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 athttp://www.apache.org/licenses/LICENSE-2.0Unless 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.Changelog0.0.12 (2012-10-15)Increase delay when starting a service. This is to give a slow VM long enough
to start 3 zopes.0.0.11 (2012-06-27)Allow arbritary text to be inserted into a cluster script (the intention is
to be able to inject comments for init systems to scan.0.0.10 (2012-03-12)Add a ‘running’ subcommand. Exit code 0 means all the services are running.
Exit code 1 means 1 server is missing, 2 means 2 are missing and so on.0.0.9 (2012-02-02)Makeforce-useroptional.0.0.8 (2011-10-04)Don’t sudo if it can be helped0.0.7 (2011-09-08)Avoid simplejson0.0.6 (2011-08-31)Fix typos0.0.4 (2011-08-26)Create the varrun directory if it doesnt existPick up ${buildout:run-directory} if its setPin simplejson0.0.3 (2011-08-23)Fix shlex split aginst unicode strings0.0.2 (2011-08-09)Added ‘user’ option to Service object so we can run different services as different usersFix tests0.0.1None?0.0.0Initial version
Package: isotoma.recipe.crond
This package providesbuildoutrecipes for the configuration of cron jobs.
It creates files that are suitable for use in /etc/cron.d.We use the system cron, so this recipe will not install cron for you.  If
you wish to install cron, usezc.recipe.cmmiperhaps.Mandatory ParameterscommandThe command to run from cron. Cron can’t handle multi-line commands, so n will become ‘ ‘.scriptInstead of command you can provide a script inline that will be saved to disk and run in the cronjob.userThe account to run the command underlocationWhere to write the cron entry toTime ParametersatOne of ‘reboot’, ‘yearly’, ‘monthly’, ‘weekly’, ‘daily’, ‘midnight’ or ‘hourly’minuteAny integer from 0 to 59hourAny integer from 0 to 23dayAny integer from 1 to 31 (must be a valid day if a month is specified)monthAny integer from 1 to 12, or the short name of the month such as ‘jan’day-of-weekAny integer from 0 to 7 (where 0 and 7 are Sunday), or a short name such as ‘mon’You must specify at least one of the above. You can use normalcronnotation here too.Optional Parametersenvironment-varsPrepare the environment that your cron job will run under, for example setting PYTHONPATHcommentsAny comments made will be prefixed with ‘#’ and included in the generated files.RepositoryThis software is available from ourrecipe repositoryon github.LicenseCopyright 2010 Isotoma LimitedLicensed 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 athttp://www.apache.org/licenses/LICENSE-2.0Unless 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: isotoma.recipe.distros
This is a fork ofplone.recipe.distrosthat uses the zc.buildout Download
API so that the lovely.buildouthttp monkey patches work on it. You probably
don’t want to use this fork!!!!OptionsurlsThe URLs of the archives to download. The archives specified in the same
part will be extracted into the same parts folder named after the part.
The full path to that folder will be available as ‘location’ from the
parts option dictionary.nested-packagesThe file names of one or more of the archives in the urls list.
This will cause only the Python packages (identified by a __init__.py) in
the top folder in the archive to be extracted into the destination.version-suffix-packagesThe file names of one or more of the archives in the urls list.
This will cause the part after the last dash to be omitted from the created
destination folder.
Package: isotoma.recipe.eggpaths
This package provides abuildoutrecipe to get the paths to the eggs that have been installed. This is useful for referencing paths within an egg in a later buildout part, such as Apache aliases to a Django media directory.The values are provided as buildout parameters in the section of which this is the recipe.For example:[eggpaths]
recipe = isotoma.recipe.eggpaths
eggs = Nose
       Django

[apache]
recipe = isotoma.recipe.apache
aliases = /media:${eggpaths:Django}/contrib/admin/mediaThis recipe will also create a text file called eggpaths.txt in the parts directory, which can be used for referenceMandatory parameterseggsThe list of eggs that you are interested in the paths forLicenseCopyright 2010 Isotoma LimitedLicensed 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 athttp://www.apache.org/licenses/LICENSE-2.0Unless 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: isotoma.recipe.facts
IntroductionThis package provides information about the host you are running buildout on.Exposed ParametershostnameThe hostname of the machine buildout is running on, as returned bysocket.gethostname()fqdnThe fully qualified domain of the machine buildout is running on, as return bysocket.getfqdn().
If no fqdn is available, this will be the same as hostname.interface.X.addressThe IP address of the network interfaceX.user.nameThe name of the account running buildoutuser.uidThe uid running buildout. Numerical.user.gidThe gid running buildout. Numerical.user.homeThe home directory of the user running buildoutvcs.typeThe type of checkout that buildout is being run from. Supports Mercurial (‘hg’), Git (‘git’) or Subversion (‘svn’), otherwise will be ‘unknown’.vcs.branchThe branch or that that buildout is being run from. Will be ‘unknown’ for unsupported VCS.Using factsThis example uses the missingbits echo recipe to print information about the current machine:[buildout]
parts = echo

[facts]
recipe = isotoma.recipe.facts

[echo]
recipe = missingbits:echo
echo =
    The hostname is ${facts:hostname}
    The fdqn is ${facts:fdqn}
    The main IP address is ${facts:interface.eth0.address}
    The VCS type is ${facts:vcs.type} and branch is ${facts:vcs.branch}
    The user is ${facts:user.name} and their home dir is ${facts:user.home}Changelog0.0.8 (2015-04-15)Nothing changed yet.0.0.7 (2014-03-12)fix bug when using without any vcs
[djay]fix bug when interface name includes a ‘:’
[djay]0.0.6 (2012-02-10)Added support for Mercurial VCS0.0.5 (2012-02-03)Force english locale so the ‘svn info’ output is parseable everywhere0.0.4 (2012-02-03)Setlsb.codenameand other lsb properties so we can make decisions
base on the distro version.0.0.3 (2011-08-30)Setuser.name,user.home,user.uidanduser.gidfactsSetvcs.branchandvcs.typeeven if the cwd isn’t Git or SVN.0.0.2 (2011-08-22)Add Git branch detection0.0.1 (2011-08-11)Detect information about vcs0.0.0 (2011-08-09)Initial versionAbility to get fqdn, hostname and ip addresses (by eth name)
Package: isotoma.recipe.gocaptain
The GoCaptain[1]buildout recipe produces a script to start and stop daemons,
similar to those you find in /etc/init.d.  By default it will inspect your
system and either write a “simple” script, such as you might produce yourself
or produce a LinuxStandard Base variation, that provides more tooling.In particular the LSB scripts will try multiple times to shut down your daemon,
and will not start it if it is already running.This package also provides a simple way to produce these scripts from other
buildout recipes - seeisotoma.recipe.varnishfor an example.The buildout recipeA simple example would be:[example]
recipe = isotoma.recipe.gocaptain
daemon = /usr/bin/example
name = example
description = example daemon for that thing i did that time
pidfile = /var/tmp/example.pid
args =
    -P ${example:pidfile}
    -w /var/tmp/example.logThis will produce a script in bin/example that launches your daemon, and shuts
it down again later, using the PID in the pidfile.OptionsThe mandatory options this recipe accepts are:daemonThe path to the daemon executable filenameThe name of the daemon, displayed in log messagesdescriptionA longer description, shown on the console during start and stoppidfileA path to a file to store the PID of the new daemon inargsThe arguments for the daemon.  These will be formatted in the output script as you provide them, with continuations provided as neededIn addition you can provide:templateA path to the template for your start/stop script.  This will be used in preference to the templates provided with this package.Calling from other codeIf you wish to use this from one of your own recipes, I suggest you do
something like:from isotoma.recipe import gocaptain
gc = gocaptain.Automatic()
f = open("/path/to/script", "w")
gc.write(f, daemon="/usr/sbin/thing",
         args="-D -P /path/to/pid",
         name="my thing", description="thing")
f.close()
os.chmod(target, 0755)The Automatic module will select the Simple or LinuxStandardBase variants, by
inspecting your system (very simplisticly!).LicenseCopyright 2010 Isotoma LimitedLicensed 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 athttp://www.apache.org/licenses/LICENSE-2.0Unless 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.[1]The name comes from Cordwainer Smith
Package: isotoma.recipe.ldap
Slapd buildout recipeThis package provides buildout_recipes for the configuration ofslapd.We use the system slapd, so this recipe will not install slapd for you.  If you
wish to install slapd, usezc.recipe.cmmiperhaps.Mandatory parametersincludesThe schema and config files to loadOptional parametersexecutableThe path to the slapd binary.  Defaults to/usr/sbin/slapd.pidfileThe location to store the pidfile. Defaults to${buildout:run-directory}/PARTNAME.pid, or${buildout:parts-directory}/PARTNAME/slapd.piddirectoryThe location to store data. Defaults to${buildout:directory}/var/PARTNAME.userThe user to run slapd as.  Defaults toopenldap.groupThe group to run slapd as.  Defaults toopenldap.indexesA list of indexes to apply to the LDAP instance.templateThe full path to the configuration file template, if you want to customise further.  Defaults to slapd.conf.j2 template in this package.Changelog0.0.1 (2011-12-01)Make interfaces/ports listened on configurable0.0.0 (2011-11-30)Initial version.
Package: isotoma.recipe.ploneprefetch
This recipe prefetches all the Plone eggs contained in a unified installer.
This vastly reduces the number of eggs that have to be installed giving Travis
a chance of actually building your code before hitting a timeout.Just do:[prefetch]
recipe = isotoma.recipe.ploneprefetch
url = http://launchpad.net/plone/4.1/4.1/+download/Plone-4.1-UnifiedInstaller-20110907.tgz
python = 2.6The python version is just to stop a python 2.6 user from downloading the
unified installer for plone 4.2 which is 2.7 only. It’s optional.