I guess the last condition of this line should be typeof options2.port !== "number", not options.port.

If OPCUA server is created without port, it throws error of expecting a valid port (number)

Works: server = new opcua.OPCUAServer({ port: 26543 });
Error: `server = new o

While some methods do validate input data, some take data as-is and can result in runtime errors or unexpected behavior.

Formalizing the restrictions, both general dataset restrictions and valid meter topologies, will allow the addition of an optional validation step for each method.

(Potentially) related issues and comments:

• nilmtk/nilmtk#564 (comment)

In the apidocs, for each module there is a section "Module contents" at the very bottom. I am not sure what it is intended for. In the build, there is nothing displayed, just the headline. Does anyone have an idea what this is for? Shall we fix it or remove it?

For example here:

https://oemof.readthedocs.io/en/stable/api/oemof.tools.html#module-oemof.tools

Is your feature request related to a problem? Please describe.
When I'm hunting for a particular variable, I'm often unsure which dataset it's in, or if PUDL has a cleaned version.

Describe the solution you'd like
It would be great to have the readthedocs site describe the tables and variables that are present in the current zenodo release. Things like table names, variable names, and

in PR53 properties were added. To have them appear in the documentation I added rst files for WindFarm and WindTurbineCluster documentation. Locally the build works as expected, but on rtd these changes don't seem to have any effect.

many of the left dropdown options cause the mapbox chart to fail with an unexpected value issue:

<img width="608" alt="screen shot 2018-02-22 at 11 53 03 am" src="https://user-images.githubusercontent.com/2789078/36555879-51

The documentation is too verbose and is also spread throughout the package. I'd like to keep local docs but link back to them all in the root readme.

Problem description

in our YAML files, we can only handle loading timeseries data if the data is formatted as e.g.:

resource: file=filename.csv or resource: file=filename.csv:columnname.

Referencing the file as follows will cause the data to be loaded in as a string without a timeseries dimension (and an exception will be raised on running the model):

`resource: file = filename.

The CLI command with sample returns "NO MODEL" rather than a model as shown in the documentation. This is with version 2.8.1 of eemeter.

The command is: eemeter caltrack --sample=il-electricity-cdd-hdd-daily

The command and results are from the documentation, in the section "Using the CLI":
https://eemeter.readthedocs.io/basics.html

I would expect the command to return the same status a

Hello,

Is there documentation on exactly how share-weights are calculated in GCAM or a portion of code that lays out the logic for how this is done? @rjplevin are working on implementing policies for electrification, and part of this process requires ensuring that the share-weights for the electric technologies are high enough to ensure the standard can be met. I have a basic understanding of h

Describe the problem

The documentation on submission of extensions does not reflect the latest thoughts on the proces.

Expected content

It should match that in the [OEP issue template](https://github.com/OSeMOSYS/OSeMOSYS/blob/master/.githu

Expected Behavior

I would have expected the Geocoding Confidence values to be the same between 2.6.0 (on the production server) and 2.6.2 (on the dev1 server)

Maybe something about how those values are created has been updated, but I wanted to record the difference while I am noticing it, and then we can figure out if this is an issue or not.

Actual Behavior

The geocoding confide

The User Guide pdf is created from rst source files, using Sphinx.
In the past, these files were hosted in a dedicated private repository,
but PR #116 moved the source files to the docs directory of this repository.

Some instructions on how to get started with rst and Sphinx are

Is it possible to build Tonatiuh against Coin3D libraries provided by the 
standard Ubuntu 12.04 software repository? If so that would be useful, and 
would significantly lower the barrier to participation.

Original issue reported on code.google.com by john....@gmail.com on 28 May 2013 at 4:42

https://github.com/LLNL/GridDyn/blob/cf850abcc921f9f1bfea917ffc03a966d64c0a6a/src/griddyn/links/hvdc.cpp#L38

A dcLink can not be set to be a slack bus, so that statement throws unconditionally. This additionally leaks dcl.

This was added in 573966f8c96ac8f15bb9ffd0f82b62c6e4d830f3, so I don't know what the expected behavior is.