The Experts below are selected from a list of 30 Experts worldwide ranked by ideXlab platform

Philipp S. Sommer - One of the best experts on this subject based on the ideXlab platform.

  • Chilipp/psyplot-conda: v1.0.1: Conda installers for psyplot - The interactive visualization framework
    2017
    Co-Authors: Philipp S. Sommer
    Abstract:

    psyplot-conda provides standalone installers for the psyplot interactive visualization framework. psyplot is an open source python project that mainly combines the plotting utilities of matplotlib (Hunter, 2007) and the data management of the xarray package (Hoyer & Hamman, 2017). The main purpose is to have a framework that allows a fast, attractive, flexible, easily applicable, easily reproducible and especially an interactive visualization of your data. The ultimate goal is to help scientists and especially climate model developers in their daily work by providing a flexible visualization tool that can be enhanced by their own visualization scripts. psyplot can be used through the python command line and through the psyplot-gui module which provides a graphical user interface for an easier interactive usage. These installers contains all necessary dependencies for psyplot, psyplot-gui, psy-simple, psy-maps and psy-reg plus the conda package for managing virtual environments. The installers have been created using using the conda constructor package and the packages from the conda-forge channel. Other ways to install psyplot can be found in the psyplot docs: http://psyplot.readthedocs.io Source files These files contain the source python code for the psyplot-conda repository (tag v1.0.1) and it's submodules psyplot (tag v1.0.0), psy-simple (tag v1.0.0), psy-maps (tag v1.0.0), psy-reg (tag v1.0.0) and psyplot-gui (tag v1.0.1). psyplot-conda-1.0.1.zip: The zipped source files including reference figures for psy-simple and psy-maps psyplot-conda-1.0.1-no-refs.zip: The zipped source files without reference figures Documentation files These files contain the documentation for psyplot, psy-maps, psy-reg, psy-simple and psyplot-gui from http://psyplot.readthedocs.io/en/latest/, downloaded on August, 21st, 2017. docs-epub.zip: Documentation files in epub format docs-pdf.zip: Documentation files in pdf format docs-html.zip: Documentation files in html format Standalone installers These installers have been created using the conda constructor package and can be used to install psyplot, psy-simple, psy-maps, psy-reg and psyplot-gui. Installation instructions can be found in the Additional Notes. psyplot-conda-1.0.1-Linux-x86-64.sh: Bash installer for 64-bit Linux systems psyplot-conda-1.0.1-MacOSX-x86-64.sh: Bash installer for 64-bit Mac OS X systems psyplot-conda-1.0.1-MacOSX-x86-64.pkg: Package installer for 64-bit Mac OS X systems psyplot-conda-1.0.1-Windows-x86-64.exe: Windows installer for 64-bit systems psyplot-conda-1.0.1-Windows-x86.exe: Windows installer for 32-bit systems psyplot-conda-1.0.1-Windows-no-shortcut-x86-64.exe: Windows installer for 64-bit systems without menu shortcut psyplot-conda-1.0.1-Windows-no-shortcut-x86.exe: Windows installer for 32-bit systems without menu shortcut Packages These files contain packages for psyplot (1.0.0.post1), psy-simple (1.0.0), psy-maps (1.0.0), psy-reg (1.0.0) and psyplot-gui (1.0.1). python-packages.zip: Python packages from pipy.org conda-packages.zip: Conda packages from https://anaconda.org/conda-forge Installation instructions for standalone installers Installation on Linux Download the bash script and open a terminal window. Type: bash '' and simply follow the instructions. For more information on the command line options type: bash '' --help It will ask you, whether you want to add a psyplot alias to your .bashrc, such that you can easily start the terminal and type psyplot to start the GUI. You can avoid this by setting NO_PSYPLOT_ALIAS=1. Hence, to install psyplot-conda without any terminal interaction, run: NO_PSYPLOT_ALIAS=1 bash '' -b -p UnInstallation on Linux Just delete the folder where you installed psyplot-conda. By default, this is $HOME/psyplot-conda, so just type: rm -rf $HOME/psyplot-conda If you added a psyplot alias to your .bashrc or chose to add the bin Directory to your PATH variable during the Installation, open your $HOME/.bashrc in an editor of your choice and delete those parts. Installation on OS X You can either install it from the terminal using a bash-script (.sh file), or you can install a standalone app using an installer (.pkg file). The bash script will install a conda Installation in your desired location. Both will create a Psyplot.app (see below). Installation using the OS X package This should be straight-forward, however Apple does not provide free Developer IDs for open-source developers. Therefore our installers are not signed and you have to give the permissions to open the files manually. The 4 steps below describe the process. Just download the .pkg file To open it, you have to Right-click on the file, then Open With, then Installer. In the appearing window, click the Open button. Follow the instructions. It will create a Psyplot.app in the specified location. To open the app the first time, change to the chosen Installation Directory for the App (by default $HOME/Applications), right-click the Psyplot app and click on Open. In the appearing window, again click on Open. Installation using the bash script Download the bash script (file ending on '.sh' for MacOSX) and open a terminal window. Type: bash '' and simply follow the instructions. For more informations on the command line options type: bash '' --help By default, the installer asks whether you want to install a Psyplot.app into your Applications Directory. You can avoid this be setting NO_PSYPLOT_APP=1. Furthermore it will ask you, whether you want to add a psyplot alias to your .bash_profile, such that you can easily start the terminal and type psyplot to start the GUI. You can avoid this by setting NO_PSYPLOT_ALIAS=1. Hence, to install psyplot-conda without any terminal interaction, run: NO_PSYPLOT_APP=1 NO_PSYPLOT_ALIAS=1 bash '' -b -p UnInstallation on OSX The unInstallation depends on whether you have used the package installer or the bash script for the Installation. Uninstall the App installed through the OS X package Just delete the app from your Applications folder. There have been no changes made to your PATH variable. Uninstall the App installed via bash script As for linux, just delete the folder where you installed psyplot-conda. By default, this is $HOME/psyplot-conda. Open a terminal and just type: rm -rf $HOME/psyplot-conda If you added a psyplot alias to your .bash_profile or chose to add the bin Directory to your PATH variable during the Installation, open your $HOME/.bash_profile in an editor of your choice and delete those parts. If you chose to add a Psyplot app, just delete the symbolic link in /Applications or $HOME/Applications. Installation on Windows Just download the installer for 64-bit or 32-bit, double click the downloaded file and follow the instructions. The Installation will create an item in the windows menu (Start -> Programs -> Psyplot) which you can use to open the GUI. You can, however, also download installers that create no shortcut from below. In any case, if you chose to modify your PATH variable during the Installation, you can open a command window (cmd) and type psyplot. UnInstallation on Windows Just double-click the Uninstall-Anaconda.exe file in the Directory where you installed psyplot-conda and follow the instructions. This will also revert the changes in your PATH variable. Acknowledgements The author thanks the Swiss National Science Foundation (SNF) for their support. Funding for the author came from the ACACIA grant (CR10I2_146314) and the HORNET grant (200021_169598)

Philipp Sommer - One of the best experts on this subject based on the ideXlab platform.

  • Chilipp/psyplot-conda: v1.0.1: Revised release with additional Windows and OS X installers
    2017
    Co-Authors: Philipp Sommer
    Abstract:

    v1.0.1 Added added changelog Added Mac OSX .pkg installer Changed Increased psyplot-gui to v1.0.1 Installation on Linux Download the bash script (file ending on '.sh' for linux) and open a terminal window. Type bash '' and simply follow the instructions. For more information on the command line options, type bash '' --help It will ask you, whether you want to add a psyplot alias to your .bashrc, such that you can easily start the terminal and type psyplot to start the GUI. You can avoid this by setting NO_PSYPLOT_ALIAS=1. Hence, to install psyplot-conda without any terminal interaction, run NO_PSYPLOT_ALIAS=1 bash '' -b -p UnInstallation on Linux Just delete the folder where you installed psyplot-conda. By default, this is $HOME/psyplot-conda, so just type rm -rf $HOME/psyplot-conda If you added a psyplot alias to your .bashrc or chose to add the bin Directory to your PATH variable during the Installation, open your $HOME/.bashrc in an editor of your choice and delete those parts. Installation on OS X You can either install it from the terminal using a bash-script (.sh file), or you can install a standalone app using an installer package (.pkg file). The bash script will install a conda Installation in your desired location. Both will create a Psyplot.app (see below). Installation using the OS X package This should be straight-forward, however Apple does not provide free Developer IDs for open-source developers. Therefore our installers are not signed and you have to give the permissions to open the files manually. The 4 steps below describe the process. Just download the package installer To open it, you have to Right-click on the file |rarr| Open With |rarr| Installer. In the appearing window, click the Open button. Follow the instructions. It will create a Psyplot.app in the specified location. To open the app the first time, change to the chosen Installation Directory for the App (by default $HOME/Applications), right-click the Psyplot app and click on Open. In the appearing window, again click on Open. Installation using the bash script Download the bash script (file ending on '.sh' for MacOSX) from the releases_ page and open a terminal window. Type bash '' and simply follow the instructions. For more informations on the command line options, type bash '' --help By default, the installer asks whether you want to install a Psyplot.app into your Applications Directory. You can avoid this be setting NO_PSYPLOT_APP=1. Furthermore it will ask you, whether you want to add a psyplot alias to your .bash_profile, such that you can easily start the terminal and type psyplot to start the GUI. You can avoid this by setting NO_PSYPLOT_ALIAS=1. Hence, to install psyplot-conda without any terminal interaction, run NO_PSYPLOT_APP=1 NO_PSYPLOT_ALIAS=1 bash '' -b -p UnInstallation on OSX The unInstallation depends on whether you have used the package installer or the bash script for the Installation. Uninstall the App installed through the OS X package Just delete the app from your Applications folder. There have been no changes made to your PATH variable. Uninstall the App installed via bash script As for linux, just delete the folder where you installed psyplot-conda. By default, this is $HOME/psyplot-conda. Open a terminal and just type rm -rf $HOME/psyplot-conda If you added a psyplot alias to your .bash_profile or chose to add the bin Directory to your PATH variable during the Installation, open your $HOME/.bash_profile in an editor of your choice and delete those parts. If you chose to add a Psyplot app, just delete the symbolic link in /Applications or $HOME/Applications. Installation on Windows Just double click the downloaded file for 64-bit or 32-bit systems and follow the instructions. The Installation will create an item in the windows menu (Start -> Programs -> Psyplot) which you can use to open the GUI. If you do not want the shortcut, download the installer without shortcut for 64-bit or 32-bit. In any case, if you chose to add the binaries to your PATH variable, you can open a command window (cmd) and type psyplot. UnInstallation on Windows Just double-click the Uninstall-Anaconda.exe file in the Directory where you installed psyplot-conda and follow the instructions

Bridger M. Mitchell - One of the best experts on this subject based on the ideXlab platform.

  • Optimal Pricing of Local Telephone Service
    The American Economic Review, 2016
    Co-Authors: Bridger M. Mitchell
    Abstract:

    Although payment for nearly all other goods and services, including toll (long distance) telephone calls, increases with greater consumption, nearly 90 percent of the residential telephone subscribers and more than half the business subscribers in the United States now pay a flat monthly rate for local calls (see Larry Garfinkel). Recently, however, the telephone companies and regulatory commissions have been moving cautiously toward imposing usage charges for local telephone calls. There is renewed interest in what is currently termed "usage-sensitive pricing"t (USP). It is due to the combined forces of inflation, increased local usage, and competition from independent firms that sell telephone terminal equipment and supply private toll lines to business customers. Under USP, the pricing of such services as telephone Installation, Directory assistance, and minutes of calling is based on incremental rather than average costs. Since World War II, technological advances have benefited long distance far more than local telephone calling. Development in microwave communications, coaxial cable, satellites, and waveguides have dramatically lowered the costs of long distance transmission. In contrast, the costs of local service have moved upward since the late 1960's at a rate not far below the general price index (see AT&T, 1975). Faced with a continuing stream of requests for local telephone rate increases, state regulatory commissions are finding the concept of tying prices to usage increasingly attractive. AT&T and some of the independent telephone carriers are beginning to test USP plans in several cities. With flat rate tariffs, increases in local calling add to carrier costs but not to their revenues. The local calling rate per subscriber has increased by an average of 2 percent for the past seven years. AT&T's chairman has stated, "We are moving more and more in the direction of usage-sensitive pricing" (see Washington Star News, p. A12), and according to newspaper accounts of AT&T management documents, the Bell System plans to phase out flat rate telephone service and begin charging for each local call in major metropolitan areas in 1978-80 (see Seattle PostIntelligencer, pp. 1, 10). Still, regulatory commissions, consumer groups, and the carriers themselves remain cautious about requiring usage-sensitive tariffs for all subscribers. The prospective gains from prices more closely related to costs are at least partially offset by the added costs of metering equipment and billing. Most telephone subscribers prefer flat rates, according to Bell System marketing surveys (see Garfinkel, p. 28). And it is by no means clear which groups of subscribers will be helped and which harmed by such revisions in local tariff structures. Will the poor end up paying more because they use their phones more? Should different prices be charged for calls at different times of day? On what bases should the monthly and per call rates be determined? The purpose of this paper is to sort out some of the questions of economic efficiency and equity that arise when changes are considered in the methods of pricing local telephone services. In Section I, I construct a * Department of economics, The Rand Corporation, and the International Institute of Management, Berlin. This study was supported under a grant from the John and Mary R.. Markle Foundation. I am indebted to Walter S. Baer for numerous contributions to this paper, to S. C. Littlechild and Patricia Munch, and to the managing editor and a referee of this Review for critical and constructive review of a draft. I have benefited as well from the comments and suggestions of James H. Alleman, Stanley M. Besen, William S. Comanor, John M. Drew, Leland L. Johnson, John A. Kay, Edward D. Lowry, Carl Pavarini, John Rolph, Ralph Turvey, and Chris Witze. Bryant Mori assisted with the computer programming. See my 1976 paper for a more extensive version of this paper, which also discusses optimal flat rate and optimal peak load tariffs.

Derek L. Schutt - One of the best experts on this subject based on the ideXlab platform.

Joe Perry - One of the best experts on this subject based on the ideXlab platform.

  • Automating the Installation and Operational Qualifications of Your SAS Applications with the SAS System
    2011
    Co-Authors: Joe Perry
    Abstract:

    Many industries require that new software Installations go through checks that they have both been installed correctly (Installation Qualification or IQ) as well as operate as intended (Operational Qualification or OQ). Modest software development projects can use one or more brute force methods of performing or ensuring the critical software qualifications of the software placed in the hands of the end-user, the application, even for modest software applications, can tax the patience of any person or company. As anyone who plans, executes or supports software validation activities knows: preparing, executing and documenting the validation processes can be time consuming and costly. Recognizing this, the SAS Institute has pre-packaged IQ and OQ routines that ease the task of performing installing SAS ® in controlled environments, saving users considerable time and money. With proper planning during the software development process, other SAS-based applications can take advantage of some of these same techniques and you can significantly improve the user’s IQ and OQ experiences. This paper discusses SAS-based automation methods to use for Installation and Operational Qualifications for use in your own software deployments; discussing and demonstrating simple methods to reduce the complexity, uncertainty and cost of installing software at your users’ site. BACKGROUND Installing, configuring and performing: Installation Qualifications, First Use Operations and Operational Qualifications can be both time consuming and subject to poor work or testing processes: compress time and errors will increase for both documentation and the quality of the work, improve work or testing as well as the time required can bust your budget. Following a manufacturing maxim “never automate a manual process…”, automation of these manual processes, though possible, will require some (possibly) significant changes to the overall system’s architecture. For example, any application’s Installation Directory must contain all of the files found in the system’s ‘manifest’, whether that list is real or virtual. The Installation Qualification confirms that the expected files and locations are, in fact, where they need to be in order for the application to work correctly. Also, some SAS Installations use a customized startup icon; with users required to manually configure the SAS startup icon for configuration parameters like: SASINITIALFOLDER, AUTOEXEC, etc.; the automated configuration routines for this process will have to be accomplished by moving these steps into a code controllable routine, these will then become part of the overall application’s code base. Likewise, the Operational Qualification, most often written out and performed by an independent party, would usually require a modification of the system’s code so it could: analyze, capture and report out the results of the, previously, manual tests performed within the OQ. This paper looks at a typical application and discusses specific tasks and code for the application of SAS-based automation routines to handle the IQ and OQ routines, first we need to look at the process design specifications.