System Setup
TinyCLR OS is the tiny operating system used by the BrainPad to run your C# and Visual Basic programs. Microsoft Visual Studio is used to write these programs on your computer and is also used by professional programmers the world over. Both TinyCLR and Visual Studio are available for free, but must be set up before using them to program the BrainPad and start having fun.
Tip
You can learn more about TinyCLR OS on the GHI Electronics website
Step 1: Install the Necessary Software
Visual Studio
The Visual Studio Community Edition is free and can be found here: Microsoft Visual Studio 2017 Community Edition.
Click on the above link an then click on the Download VS Community 2017 button. After downloading is complete, run the file. If you are asked, allow the program to make changes to your device.
When the installation program shows the Workloads
screen, select .NET desktop development
(you should see a check mark in the .NET desktop development
box) and then click the Install
button.
After installation is complete, click on the Launch
button. You will be asked to sign in or sign up for Visual Studio developer services. You can either sign in (or sign up) now or click the 'Not now, maybe later' option. You will then be asked to pick a color scheme and Visual Studio will start.
TinyCLR OS Project System.
If Visual Studio is open, close it before continuing with the TinyCLR installation.
Download the TinyCLR Visual Studio Project System. After the download is complete, click on the up arrow next to the download name at the bottom of the screen as shown below.
Then select Open
from the pop-up menu.
In the VSIX Installer
dialog box click the Install
button.
Download and Install the TinyCLR Nuget Packages
- Since TinyCLR OS is still so new, we haven't yet uploaded any packages to NuGet. Download the newest libraries, extract the archive, and place them in a local NuGet feed.
- Connect your device to your PC using a USB cable (make sure your device has the latest firmware installed).
- Start Visual Studio and create a new
TinyCLR Application
underC# > TinyCLR
. New to Visual Studio or C#? Take a look at the getting started guide from Microsoft. Right click on your Project in the Solution Explorer and select
Manage NuGet Packages
. If the Solution Explorer window is not visible, open it by selectingSolution Explorer
in theView
menu.Select the
Package Source
settings icon.Click the
+
button to add a new Package source.Select the location where the NuGet packages are stored locally, by pressing the
...
button.After Selecting the local folder where the downloaded NuGet packages are, you can select the
Installed
Tab to view the installed NuGet Packages.Selecting the
Browse
tab will show all the NuGet packages located in your local NuGet feed. Those installed are noted with a green check mark in front of the name.To install one of the packages click on the package name, click the check box to the right under "Version(s)," and click on the
Install
button.Accept the licensing agreement to install the package.
And, that's it! You're now ready to start programming using TinyCLR OS.
Step 2: Prepare the BrainPad
Tip
If you have the original BrainPad Concept/Prototype the setup is slightly different. See the Older BrainPad page for more details.
To prepare the BrainPad you only need to install the latest firmware as described below.
- Download and save the latest TinyCLR OS firmware for the BrainPad from Downloads. We recommend saving the firmware file on your desktop.
- Connect the BrainPad to your computer using a micro USB cable. The power (PWR) light on the BrainPad should be on.
- Press and hold the RESET button on the BrainPad for at least three seconds until the Light Bulb on the BrainPad lights up green.
- A window will open named
BrainPad2
. Drag the firmware file from step 1 into this window. - The Light Bulb on the BrainPad will flicker and a progress gauge will appear on the computer screen.
- It only takes a few seconds for the firmware to be copied to the BrainPad. When it is done, the green light on the BrainPad will stop flickering and the
BrainPad2
window will close. - Congratulations! Your BrainPad is now running the latest firmware!
Note
The BrainPad comes with a "bootloader" pre-installed. You shouldn't have to reinstall it unless you are an advanced user using advanced programming techniques. Check out our bootloader page to find out more.
Going Beyond!
Congratulations!  You have the option of using the C# programming language or the Visual Basic programming language. If you are not sure which one to pick, C# is used more often in the professional world and is recommended for those serious about learning programming. Visual Basic is easier to use -- especially for beginners. We use C# for our own software development, but we usually start with Visual Basic for those who are new to programming.
You are not locked in to one language -- you can freely switch between C# and Visual Basic.
To give you a better idea, here is code that counts from 1 to 10 on the BrainPad display in C#:
namespace Counter {
class Program {
public void Main() {
for (int count = 1; count < 11; count++) {
BrainPad.Display.DrawNumberAndShowOnScreen(0, 0, count);
BrainPad.Wait.Seconds(1);
}
}
}
}
And here is the equivalent code in Visual Basic:
Class Program
Public Sub Main()
For count = 1 To 10
BrainPad.Display.DrawNumberAndShowOnScreen(0, 0, count)
BrainPad.Wait.Seconds(1)
Next count
End Sub
End Class
Click on a link below to get started:
You are on the documentation website for the BrainPad. The main website is found at www.brainpad.com


Toggle navigation
Stack
Home
How IT Works
JoinUs
Who we are?
Contact Us
Get In Touch
Let's have a chat
Drop us a line
Message
Get in touch
You can Get in Touch with NTEP by connecting to:
Aakash Shukla
<EMAIL_ADDRESS>9685354410
Aniket Shukla
<EMAIL_ADDRESS>7000569010


Functions¶
Table of Contents
ANOVA and T-test¶
|
One-way and N-way ANOVA. |
|
ANCOVA with one or more covariate(s). |
|
One-way and two-way repeated measures ANOVA. |
|
Epsilon adjustement factor for repeated measures. |
|
Mixed-design (split-plot) ANOVA. |
|
One-way Welch ANOVA. |
|
Two One-Sided Test (TOST) for equivalence. |
|
T-test. |
Bayesian¶
|
Bayes factor of a binomial test with \(k\) successes, \(n\) trials and base probability \(p\). |
|
Bayes Factor of a T-test. |
|
Bayes Factor of a Pearson correlation. |
Circular¶
|
Element-wise conversion of arbitrary-unit circular quantities to radians. |
|
Transforms n-axial data to a common scale. |
|
Correlation coefficient between two circular variables. |
|
Correlation coefficient between one circular and one linear variable random variables. |
|
Mean direction for (binned) circular data. |
|
Mean resultant vector length for circular data. |
|
Rayleigh test for non-uniformity of circular data. |
|
V test for non-uniformity of circular data with a specified mean direction. |
Contingency¶
|
Chi-squared independence tests between two categorical variables. |
|
Performs the exact and approximated versions of McNemar’s test. |
|
Generates a 2x2 contingency table from a |
Correlation and regression¶
|
(Robust) correlation between two variables. |
|
Pairwise (partial) correlations between columns of a pandas dataframe. |
|
Partial and semi-partial correlation. |
|
Partial correlation matrix ( |
|
Correlation matrix of a dataframe with p-values and/or sample size on the upper triangle ( |
|
Distance correlation between two arrays. |
|
Repeated measures correlation. |
|
(Multiple) Linear regression. |
|
(Multiple) Binary logistic regression. |
|
Mediation analysis using a bias-correct non-parametric bootstrap method. |
Distribution¶
|
Anderson-Darling test of distribution. |
|
Geometric standard (Z) score. |
|
Test equality of variance. |
|
Univariate normality test. |
|
Mauchly and JNS test for sphericity. |
Effect sizes¶
|
Calculate effect size between two set of observations. |
|
Compute effect size from a T-value. |
|
Conversion between effect sizes. |
|
Parametric confidence intervals around a Cohen d or a correlation coefficient. |
|
Bootstrapped confidence intervals of univariate and bivariate functions. |
Multiple comparisons and post-hoc tests¶
|
Pairwise (partial) correlations between columns of a pandas dataframe. |
|
Pairwise T-tests. |
|
Pairwise Tukey-HSD post-hoc test. |
|
Pairwise Games-Howell post-hoc test. |
|
P-values correction for multiple comparisons. |
Multivariate tests¶
|
Test equality of covariance matrices using the Box’s M test. |
|
Henze-Zirkler multivariate normality test. |
|
Hotelling T-squared test (= multivariate T-test) |
Non-parametric¶
|
Cochran Q test. |
|
Friedman test for repeated measurements. |
|
Kruskal-Wallis H-test for independent samples. |
|
Median Absolute Deviation (MAD) along given axis of an array. |
Robust outlier detection based on the MAD-median rule. |
|
|
Mann-Whitney U Test (= Wilcoxon rank-sum test). |
|
Wilcoxon signed-rank test. |
|
Harrell-Davis robust estimate of the \(q^{th}\) quantile(s) of the data. |
Others¶
|
Pretty display of table. |
|
Remove missing values along a given axis in one or more (paired) numpy arrays. |
|
Read example datasets. |
List available example datasets. |
|
Reset Pingouin’s default global options (e.g. |
Plotting¶
|
Generate a Bland-Altman plot to compare two sets of measurements. |
|
Plot the circular mean and vector length of a set of angles on the unit circle. |
|
Paired plot. |
|
Shift plot. |
|
Plot a repeated measures correlation. |
|
Quantile-Quantile plot. |
Power analysis¶
|
Evaluate power, sample size, effect size or significance level of a one-way balanced ANOVA. |
|
Evaluate power, sample size, effect size or significance level of a balanced one-way repeated measures ANOVA. |
|
Evaluate power, sample size, effect size or significance level of chi-squared tests. |
|
Evaluate power, sample size, correlation coefficient or significance level of a correlation test. |
|
Evaluate power, sample size, effect size or significance level of a one-sample T-test, a paired T-test or an independent two-samples T-test with equal sample sizes. |
|
Evaluate power, effect size or significance level of an independent two-samples T-test with unequal sample sizes. |
Reliability and consistency¶
|
Cronbach’s alpha reliability measure. |
|
Intraclass correlation. |


- s(String) - Static method in class in.definex.Console.Log
-
Logs success in green.
- saveClient(Client) - Static method in class in.definex.Database.Core.ClientDatabase
-
- SaveConfig(String, String) - Method in class in.definex.Database.Configuration
-
String/int/float/boolean overload to save configuration
- SaveConfig(String, int) - Method in class in.definex.Database.Configuration
-
- SaveConfig(String, float) - Method in class in.definex.Database.Configuration
-
- SaveConfig(String, boolean) - Method in class in.definex.Database.Configuration
-
- saveGroup(ChatGroup) - Static method in class in.definex.Database.Core.ChatGroupDatabase
-
- saveToDatabase() - Method in class in.definex.ChatSystem.Client
-
If client doesn't exist int the database, saves it
- Schedule - Class in in.definex.Scheduler
-
Schedule
Executes a ScheduleTask at specified date and time.
- Schedule(ScheduleTask, String, Long) - Constructor for class in.definex.Scheduler.Schedule
-
Constructor
Should be of pattern specifed by DATE_PATTERN (yyyy.MM.dd.HH.mm.ss)
- Schedule(ScheduleTask, String) - Constructor for class in.definex.Scheduler.Schedule
-
- ScheduleDatabase - Class in in.definex.Scheduler
-
Database class for Scheduler.
- ScheduleDatabase() - Constructor for class in.definex.Scheduler.ScheduleDatabase
-
- ScheduleManager - Class in in.definex.Scheduler
-
ScheduleManager
Maintains a list of Schedule in name value BiMap
- ScheduleManager() - Constructor for class in.definex.Scheduler.ScheduleManager
-
- ScheduleTask - Class in in.definex.Scheduler
-
ScheduleTask
Task that can be schedules using Schedule and ScheduleManager,
Must only contain members who is Implemented by Serializable or should have transient keyword.
- ScheduleTask() - Constructor for class in.definex.Scheduler.ScheduleTask
-
- selectClientWithAlias - Static variable in class in.definex.Database.Core.ClientDatabase
-
- sendButton - Static variable in class in.definex.String.XPaths
-
- SendMessageAction - Class in in.definex.Action.Core
-
SendMessageAction
Action used to send message to a chat group
Created by adam_ on 01-12-2017.
- SendMessageAction(ChatGroup, String) - Constructor for class in.definex.Action.Core.SendMessageAction
-
- setAlias(String) - Method in class in.definex.ChatSystem.Client
-
Setters
- SetAliasCommand - Class in in.definex.Feature.Accounts
-
- SetAliasCommand() - Constructor for class in.definex.Feature.Accounts.SetAliasCommand
-
- setChromeProfileLoc(String) - Method in class in.definex.Looper
-
- setCompleteActionCallback(CompleteActionCallback) - Method in class in.definex.Action.Action
-
Sets callback that is called after the action has been performed
- setDate(String) - Method in class in.definex.Scheduler.Schedule
-
- SetDebug(boolean) - Static method in class in.definex.Console.Log
-
Changes the debug setting
Changed using "1log on|off" command
- setReScheduleDeltaTime(Long) - Method in class in.definex.Scheduler.Schedule
-
Setters
- setResponseByteSize(int) - Method in class in.definex.NetworkJob.NetworkJobManager
-
Change the default number of bytes(1024) for the incoming response.
- ShareCaptionTextInput - Static variable in class in.definex.String.XPaths
-
- ShareSendIcon - Static variable in class in.definex.String.XPaths
-
- ShowAvailableFeatureCommand - Class in in.definex.Feature.GroupConfig
-
Created by adam_ on 04-12-2017.
- ShowAvailableFeatureCommand() - Constructor for class in.definex.Feature.GroupConfig.ShowAvailableFeatureCommand
-
- showAvailDescription - Static variable in class in.definex.String.FeatureAndCommandDescription
-
- showAvailTemplateExample - Static variable in class in.definex.String.FeatureAndCommandDescription
-
- Split(String) - Static method in class in.definex.Feature.CommandAndArgs
-
Splits text to command and arguments
- start() - Method in class in.definex.Looper
-
Method called to start the program from main
Waits wait for whatsapp to initialize (scan qr code)
then runs the init() method
then runs checkerAndActionThread and console thread
then waits for the threads to exit
- Strings - Class in in.definex.String
-
Strings
response strings for commands
Created by adam_ on 30-11-2017.
- Strings() - Constructor for class in.definex.String.Strings
-
- succesffullyAddedFeature - Static variable in class in.definex.String.Strings
-
- successfullyChangedRole - Static variable in class in.definex.String.Strings
-
- successfullyRegisteredFormat - Static variable in class in.definex.String.Strings
-
- successfullyRemovedFeature - Static variable in class in.definex.String.Strings
-


{% extends 'layouts/application.html' %} {% import "items/profile/profile-head.html" as head %} {% import "items/profile/profile-about.html" as about %} {% import "items/profile/profile-tabs.html" as tabs %} {% import "items/messages/message-button-container.html" as buttonContainer %} {% block pageClass %}{{ 'page--navbar-overlap has-message-button' }}{% endblock %} {% block content %}


{% extends "base.html" %} {% block content %}
Through this endeavor we have come to value:
Together, these elements build the foundation of a Small Act capable of transforming people's lives.
Get involved »


GABBA GABBA, HEY!!! GABBA GABBA, HEY!!! GABBA GABBA, HEY!!! GABBA GABBA, HEY!!! GABBA GABBA, HEY!!! GABBA GABBA, HEY!!!
The Ramones formed in 1975 in New York City, playing their earliest shows at the legendary bar and music venue CBGS.
Though the band achieved modest success during their lifetimes they are now widely acknowledged as one of the greatest and most original rock bands of all time.
The Ramones' style broke free of the stadium rock and disco music that was dominating the airwaves in the mid 1970s bringing a raw energy evocative of rocks & roll's early days,
while originating a new style of music that would become known as punk rock. Their influence continues to this day and their spirit lives on.
Tommy, Johnny, Joey, Dee Dee - The Ramones.
Bio from 1975 as written by Tommy Ramone
Ramones Rock & Roll Hall of Fame Page


@@include('app/partials/head.tpl', { "title": "Home page", "description": "I am a main page" })
Link to About page


Specify a collection of font families. The first font family supported
by the relevant device (i.e., the device that is open, or will be opened, at
plotting time) is used by thematic. If a given font family is not supported
by the default, but is a Google Font and
install = TRUE
, the font will be downloaded, cached, and registered
for use the showtext and ragg packages.
font_spec( families = "", scale = 1, install = is_installed("ragg") || is_installed("showtext"), update = FALSE, quiet = TRUE )
| families | a character vector of font families. |
|---|---|
| scale | numerical constant applied to font sizes. |
| install | whether to download and register font |
| update | if |
| quiet | whether to suppress download messages. |
the input arguments as a list.


The following applications have been submitted for your review.
Click
| Application | Applying Business | Establishment Address | ||
|---|---|---|---|---|
| {{i+1}} |
{{item?.establishmentName}}
{{item?.applicationType?.name}}
Job Number: {{item?.jobNumber}}
|
{{item?.applicant?.name}}
|
{{item?.establishmentAddressStreet}}
{{item?.establishmentAddressCity}}
{{item?.establishmentAddressPostalCode}}
|
Date Sent: {{item.dateApplicantSentToLG | date : 'dd MMM yyyy'}}
|
The following applications have been submitted for your review.
| Application | Applying Business | Establishment Address | ||
|---|---|---|---|---|
| {{i+1}} |
{{item?.establishmentName}}
{{item?.applicationType?.name}}
Job Number: {{item?.jobNumber}}
|
{{item?.applicant?.name}}
|
{{item?.establishmentAddressStreet}}
{{item?.establishmentAddressCity}}
{{item?.establishmentAddressPostalCode}}
|
|
You have indicated your intent to accept the below application(s). LCRB requires documentation of the resolution assessment within 90 days.
If you are ready to provide this information, click
| Application | Applying Business | Address | Provide Resolution | 90 Day Counter | |
|---|---|---|---|---|---|
| {{i+1}} |
{{item?.establishmentName}}
{{item?.applicationType?.name}}
Job Number: {{item?.jobNumber}}
|
{{item?.applicant?.name}}
|
{{item?.establishmentAddressStreet}}
{{item?.establishmentAddressCity}}
{{item?.establishmentAddressPostalCode}}
|
|
{{get90dayCount(item?.lGDecisionSubmissionDate)}} days left |
There are currently no applications awaiting your review.
The following applications are resolved.


Google Earth Enterprise Documentation Home | Portable
Custom folders
By default, GEE Portable stores cut globes in the Apache Document root of the GEE Server at /opt/google/gehttpd/htdocs/cutter/globes
. However, you can move the portable globes folder to a custom location. You might want to do this, for example, if this path is within a volume with limited storage space and you have space available in a separate volume.
Before you begin
- Install and configure GEE Server on the machine that will support users who create portable globes.
- Identify the path to your globes folder. This can be the same mount point for external storage of source data or the GEE Server Publish Root.
- Gain access to an account with root-level privileges.
To create a custom globes folder:
- Make sure that no globe cutting operations are in progress. Creating a custom folder makes modifications directly to the folder where portable globes are hosted and can interfere with any ongoing globe cutting operations.
- Stop the GEE Server service:
sudo /etc/init.d/geserver stop
- Use either of the methods below to set up your custom folder:
- Create a new folder:
mkdir /gevol/src/globes
- Move the original folder to a storage volume:
mv /opt/google/gehttpd/htdocs/cutter/globes /gevol/src/globes
- Create a new folder:
- Create a symbolic link from the custom folder to the original folder location:
ln -sf /gevol/src/globes /opt/google/gehttpd/htdocs/cutter/globes
- Change ownership of the custom folder to
geapacheuser:gegroup
and change permissions to 755 (rwxr-wr-w):
chown -R geapacheuser:gegroup /gevol/src/globes
chmod -R 755 /gevol/src/globes
- Start the GEE Server service.
- To test that globe cutting works, load the GEE Globe Cutting web page and either create a new portable globe or test with an existing globe. If you have an existing globe, click List globes and maps directory in the GEE Globe Cutting web page and make sure that your globe appears there.


{% load special_sauce %}
{{product.quantity_purchased}} already purchased.
{{product.part}} of {{product.total_parts}}
{% endif %}{{product.title}} -
{{product.subtitle}}
Price: {{product.price}}
{{product.description}}
Included with Comp
{% endif %}


{% extends 'base/thesis_dashboard_base.html' %} {% load static %} {% block title %} {{ block.super }} | Invite Group Members {% endblock title %} {% block page_title %}
{{ studentgroup.md5hash }}
P.S. The code is case-sensitive.
{% if studentgroup.approved %}
Your group has been already approved by admin.
Contact admin if you have to add a new group member.


|
geopm
|
#include <stddef.h>
Go to the source code of this file.
Functions | |
| int | geopm_endpoint_create (const char *endpoint_name, struct geopm_endpoint_c **endpoint) |
| Create an endpoint object for other API functions. More... | |
| int | geopm_endpoint_destroy (struct geopm_endpoint_c *endpoint) |
| Release resources associated with endpoint. More... | |
| int | geopm_endpoint_open (struct geopm_endpoint_c *endpoint) |
| Create shmem regions within the endpoint for policy/sample handling. More... | |
| int | geopm_endpoint_close (struct geopm_endpoint_c *endpoint) |
| Destroy shmem regions within the endpoint. More... | |
| int | geopm_endpoint_agent (struct geopm_endpoint_c *endpoint, size_t agent_name_max, char *agent_name) |
| Check if an agent has attached. More... | |
| int | geopm_endpoint_wait_for_agent_attach (struct geopm_endpoint_c *endpoint, double timeout) |
| Blocks until an agent has attached or the timeout is reached. More... | |
| int | geopm_endpoint_stop_wait_loop (struct geopm_endpoint_c *endpoint) |
| Stops any current wait loops the endpoint is running. More... | |
| int | geopm_endpoint_reset_wait_loop (struct geopm_endpoint_c *endpoint) |
| Resets the endpoint to prepare for a subsequent call to geopm_endpoint_wait_for_agent_attach(). More... | |
| int | geopm_endpoint_profile_name (struct geopm_endpoint_c *endpoint, size_t profile_name_max, char *profile_name) |
| Check profile name for an attached job. More... | |
| int | geopm_endpoint_num_node (struct geopm_endpoint_c *endpoint, int *num_node) |
| Get the number of nodes managed by the agent. More... | |
| int | geopm_endpoint_node_name (struct geopm_endpoint_c *endpoint, int node_idx, size_t node_name_max, char *node_name) |
| Get the hostname of the indexed compute node. More... | |
| int | geopm_endpoint_write_policy (struct geopm_endpoint_c *endpoint, size_t num_policy, const double *policy_array) |
| Set the policy values for the agent to follow. More... | |
| int | geopm_endpoint_read_sample (struct geopm_endpoint_c *endpoint, size_t num_sample, double *sample_array, double *sample_age_sec) |
| Get a sample from the agent and amount of time that has passed since the agent last provided an update. More... | |
| int geopm_endpoint_agent | ( | struct geopm_endpoint_c * | endpoint, |
| size_t | agent_name_max, | ||
| char * | agent_name | ||
| ) |
Check if an agent has attached.
| [in] | endpoint | Object created by call to geopm_endpoint_create(). |
| [in] | agent_name_max | Number of bytes allocated for the agent_name string. |
| [out] | agent_name | Name of agent if one has attached to the endpoint. If no agent has attached string is unaltered. |
| int geopm_endpoint_close | ( | struct geopm_endpoint_c * | endpoint | ) |
Destroy shmem regions within the endpoint.
| [in] | endpoint | Object created by call to geopm_endpoint_create(). |
| int geopm_endpoint_create | ( | const char * | endpoint_name, |
| struct geopm_endpoint_c ** | endpoint | ||
| ) |
Create an endpoint object for other API functions.
| [in] | endpoint_name | Shared memory key substring used to create an endpoint that an agent can attach to. |
| [out] | endpoint | Opaque pointer to geopm_endpoint_c object, or NULL upon failure. |
| int geopm_endpoint_destroy | ( | struct geopm_endpoint_c * | endpoint | ) |
Release resources associated with endpoint.
Additionally will send a signal to the agent that the manager is detaching from the policy and will no longer send updates.
| [in] | endpoint | Object to be destroyed which was previously created by call to geopm_endpoint_create(). |
| int geopm_endpoint_node_name | ( | struct geopm_endpoint_c * | endpoint, |
| int | node_idx, | ||
| size_t | node_name_max, | ||
| char * | node_name | ||
| ) |
Get the hostname of the indexed compute node.
| [in] | endpoint | Object created by call to geopm_endpoint_create() that has reported an attached agent. |
| [in] | node_idx | the index from zero to the value returned by geopm_agent_num_node() - 1. |
| [in] | node_name_max | Number of bytes allocated for the node_name string. |
| [out] | node_name | The compute node hostname. |
| int geopm_endpoint_num_node | ( | struct geopm_endpoint_c * | endpoint, |
| int * | num_node | ||
| ) |
Get the number of nodes managed by the agent.
| [in] | endpoint | Object created by call to geopm_endpoint_create() that has reported an attached agent. |
| [out] | num_node | Number of compute nodes controled by attached agent. |
| int geopm_endpoint_open | ( | struct geopm_endpoint_c * | endpoint | ) |
Create shmem regions within the endpoint for policy/sample handling.
| [in] | endpoint | Object created by call to geopm_endpoint_create(). |
| int geopm_endpoint_profile_name | ( | struct geopm_endpoint_c * | endpoint, |
| size_t | profile_name_max, | ||
| char * | profile_name | ||
| ) |
Check profile name for an attached job.
| [in] | endpoint | Object created by call to geopm_endpoint_create(). |
| [in] | profile_name_max | Number of bytes allocated for the profile_name string. |
| [out] | profile_name | Profile name of the job if one has attached to the endpoint. If no agent has attached string is unaltered. |
| int geopm_endpoint_read_sample | ( | struct geopm_endpoint_c * | endpoint, |
| size_t | num_sample, | ||
| double * | sample_array, | ||
| double * | sample_age_sec | ||
| ) |
Get a sample from the agent and amount of time that has passed since the agent last provided an update.
| [in] | endpoint | Object created by call to geopm_endpoint_create() that has reported an attached agent that provides samples (i.e. value given by geopm_agent_num_sample() is greater than zero). |
| [out] | sample_array | Array of sampled values provide by the agent. |
| [out] | timestamp | The timestamp of the agent's last update to the sample. |
| int geopm_endpoint_reset_wait_loop | ( | struct geopm_endpoint_c * | endpoint | ) |
Resets the endpoint to prepare for a subsequent call to geopm_endpoint_wait_for_agent_attach().
| [in] | endpoint | Object created by call to geopm_endpoint_create(). |
| int geopm_endpoint_stop_wait_loop | ( | struct geopm_endpoint_c * | endpoint | ) |
Stops any current wait loops the endpoint is running.
| [in] | endpoint | Object created by call to geopm_endpoint_create(). |
| int geopm_endpoint_wait_for_agent_attach | ( | struct geopm_endpoint_c * | endpoint, |
| double | timeout | ||
| ) |
Blocks until an agent has attached or the timeout is reached.
| [in] | endpoint | Object created by call to geopm_endpoint_create(). |
| [in] | timeout | Timeout in seconds. |
| int geopm_endpoint_write_policy | ( | struct geopm_endpoint_c * | endpoint, |
| size_t | num_policy, | ||
| const double * | policy_array | ||
| ) |
Set the policy values for the agent to follow.
| [in] | endpoint | Object created by call to geopm_endpoint_create() that has reported an attached agent. |
| [in] | policy_array | Array of length returned by geopm_agent_num_policy() specifing the value of each policy parameter. |


My Running Story || 11/2/2020
Read more here
The Details of Injuries || 10/30/2020
Read more here
A Running Shoe Review || 10/30/2020
Read more here
The Power of a Day || 10/30/2020
Read more here
How has the Price for TV sets changed over the years? || 10/30/2020
Read more here
The Key to Becoming a Speed Endurance Legend || 3/26/2020
Read more here


By default, time slots are time of the day-based, you can change it to time of the day + day of the week. That means scheduling 7x the number of time slots. If you change from daily to weekly, the current schedule will be repeated 7 times. If you change from weekly to daily, many of the slots will be deleted.
Allows programs to play a bit late if the previous program took longer than usual. If a program is too late, Flex is scheduled instead.
Ensures programs have a nice-looking start time, it will add Flex time to fill the gaps.
Usually slots need to add flex time to ensure that the next slot starts at the correct time. When there are multiple videos in the slot, you might prefer to distribute the flex time between the videos or to place most of the flex time at the end of the slot.
Maximum number of days to precalculate the schedule. Note that the length of the schedule is also bounded by the maximum number of programs allowed in a channel.


| Number of Classes | Line Coverage | Mutation Coverage |
|---|---|---|
| 11 | 54% | 28% |
| Name | Line Coverage | Mutation Coverage |
|---|---|---|
| FileInfo.java | 70% |
33% |
| PamFileInfo.java | 88% |
33% |
| PamWriter.java | 0% |
0% |
| PbmFileInfo.java | 76% |
44% |
| PbmWriter.java | 0% |
0% |
| PgmFileInfo.java | 66% |
24% |
| PgmWriter.java | 0% |
0% |
| PnmImageParser.java | 64% |
57% |
| PpmFileInfo.java | 62% |
24% |
| PpmWriter.java | 0% |
0% |
| WhiteSpaceReader.java | 96% |
87% |


- the assertion graph containing the info related to the scientific statement central to the nanopublication; the provenance graph containing information about the origin and creation process of the assertion;
- the publication info graph including the metadata about the creation and publishing of the nanopublication.
These three named graphs are connected one to the other by means of an additional named graph called the head graph.
The main goals of the nanopublication model are to promote interoperability among scientific results, to promote data integration and trustworthiness, to ease the access to a scientific statement and to enable the citation of atomic statements allowing for fine-grained citation metrics on the level of individual claims.


|
Hi,
Your cost per transaction dataset is out of date.
Please upload data at admin.performance.service.gov.uk
Thanks,
Performance Platform team
Details
-
Dashboard: Waste carrier registrations
-
Dataset: waste_carriers_registration_cost_per_transaction
-
Most recent data: 3 to 10 November 2014
To unsubscribe, email<EMAIL_ADDRESS>|


What do you want help with? For starters, I can explain:
To ask me a question, type help <keyword>
where <keyword>
is the thing you want to learn more about
If there's anything else you need to ask, I have a keyword lookup system as well; For example, if you wanted to learn about opening zip files, you could say help zip
.
This area on the right is a little more complicated. At the top is the navbar: it shows the long version of your current path, as well as a short description of your current directory (If a description has been set, that is!).
The place where these messages are appearing is called the chat buffer. This will show the back and fourth between you and me (helpbot), or between you and the bot that executes commands (shellbot)
Lastly, there's the command prompt, at the bottom of this area. As you type, text will appear down there. you can press enter to send the command to either me or shellbot.
That's all for now! If you're just getting started, try asking me about moving around the filesystem withhelp navigation
, or help files
.
mv <files> <target>
Moves one or many files. Can also be used to rename a file.
If <files>
is more than one element, <target>
must be a directory.
cd <directory>
Changes your current working directory. You can use it to move around the filesystem.


We, AHM-Brands LLC are operates https://www.ahm-brands.com. This page informs you of our policies regarding the collection, use and disclosure of Personal Information we receive from users of the ahm-brands.com.
We use your Personal Information only for providing and improving the Site. By using the Site, you agree to the collection and use of information in accordance with this policy.While using our site, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you. Personally identifiable information may include, but is not limited to your name ("Personal Information").
Like many site operators, we collect information that your browser sends whenever you visit our Site ("Log Data").
This Log Data may include information such as your computer's Internet Protocol ("IP") address, browser type, browser version, the pages of our Site that you visit, the time and date of your visit, the time spent on those pages and other statistics.
In addition, we may use third party services such as Google Analytics that collect, monitor and analyze this site.
Cookies are files with small amount of data, which may include an anonymous unique identifier. Cookies are sent to your browser from a web site and stored on your computer's hard drive.
Like many sites, we use "cookies" to collect information. You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Site.
The security of your Personal Information is important to us, but remember that no method of transmission over the Internet, or method of electronic storage, is 100% secure. While we strive to use commercially acceptable means to protect your Personal Information, we cannot guarantee its absolute security.
This Privacy Policy is effective as of 25 May 2018 and will remain in effect except with respect to any changes in its provisions in the future, which will be in effect immediately after being posted on this page.
We reserve the right to update or change our Privacy Policy at any time and you should check this Privacy Policy periodically. Your continued use of the Service after we post any modifications to the Privacy Policy on this page will constitute your acknowledgment of the modifications and your consent to abide and be bound by the modified Privacy Policy.
If we make any material changes to this Privacy Policy, we will notify you either through the email address you have provided us, or by placing a prominent notice on our website.
If you have any questions about this Privacy Policy, please contact us at sales@ahm-brands.com


QR Encoder / Decoder
Decode secret QR code messages that your friends have sent you, using the key they provided you with.
If the message contains a lot of '�' or doesn't make sense, check the encryption key.
Looking for the
encoder
?
Upload a QR code image to decode:
Insert the encryption key:
Most encryption keys use the following characters:
[a-z][A-Z][0-9][!@#$%'*+-/=?^_`{|}~.]
Decode QR Code
File type:
Decoded QR code contents:


Ukraine watchdog accuses presidential staffer of graft
KIEV, Nov 13 — A Ukrainian anti-corruption watchdog has accused a member of President Volodymyr Zelensky’s staff of bribery after the political novice vowed to tackle the country’s notoriously rampant graft.
The National Anti-Corruption Bureau (NABU) said it caught the official and several accomplices receiving a US$150,000 (RM621,375) bribe in a sting operation yesterday.
Investigators said this was half the amount of a bribe the group had solicited for securing a job at state energy giant Naftogaz.
Ukrainian media named the detained official as Svitlana Kondzelya, an employee in the presidency since 2009 who currently heads a department dealing with citizens’ requests.
Prominent Ukrainian news website Ukrainska Pravda quoted a source as saying that Kondzelya had boasted she could “solve any kind of problem through her contacts in the (president’s) office”.
The president’s Facebook page confirmed the detentions without naming the suspect.
“There is no ‘us’ and ‘them’ for the head of state. Corruption must be eradicated,” it said.
Those arrested yesterday also included a former deputy culture minister who served in 2011, the NABU statement said.
At that time Ukraine was governed by pro-Russian President Viktor Yanukovych.
Zelensky was elected president on promises of change after he accused predecessor Petro Poroshenko of failing to curb corruption in the post-Soviet state.
While the new authorities have tightened anti-corruption legislation and launched proceedings against several senior officials, both former and current, Zelensky’s opponents accuse his team of targeting only officials with close ties to Poroshenko.
According to Transparency International, Ukraine is ranked 120th out of 180 on the NGO’s corruption perception index, faring better than Russia (in 138th place) but still falling far behind its European Union neighbours. — AFP


ACCEPT
Index
Return to Main Contents
Example
NAME
accept - accept a connection on a socket
SYNOPSIS
#include <lwip/sockets.h>
int accept(int s, struct sockaddr *addr, int *addrlen);
DESCRIPTION
The argument s is a socket that has been created with
socket,
bound to an address with bind, and is listening
for connections after a listen.
The accept function extracts the first connection request on the queue
of pending connections, creates a new socket with the same properties as
s and allocates a new file descriptor for the socket. If no pending
connections are present on the queue, and the socket is not marked as
non-blocking, accept blocks the caller until a connection is present.
If the socket is marked non-blocking and no pending connections are present on
the queue, accept returns the error as described below.
The accepted socket may not be used to accept more connections.
The original socket s remains open.
The argument addr is a result parameter that is filled in with the
address of the connecting entity, as known to the communications layer.
The exact format of the addr parameter is determined by the domain in
which the communication is occurring. The addrlen is a value-result
parameter; it should initially contain the amount of space pointed to by addr; on return it will contain the actual length (in bytes) of the address
returned. This call is used with connection-based socket types, currently
with SOCK_STREAM.
It is possible to
select a socket for the purposes of doing an
accept by selecting it for read.
RETURN VALUES
The call returns -1 on error and the specific error number can be obtained by
calling the function GetSocketError. In
multi-threaded environments the last error number is held seperately for
each thread.
ERRORS
- EINVAL
-
The descriptor is invalid.
- ENOTSOCK Not Supported
-
Argument is not a valid socket.
- EOPNOTSUPP Not Supported
-
The referenced socket is not of type
SOCK_STREAM.
- EFAULT
-
The
addr
parameter is not in a writable part of the user address space.
- EWOULDBLOCK Not Supported
-
The socket is marked non-blocking and no connections are
present to be accepted.
SEE ALSO
bind,
connect,
listen,
select,
socket
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- RETURN VALUES
-
- ERRORS
-
- SEE ALSO
-


{% extends 'base.html'%} {% import "bootstrap/wtf.html" as wtf %} {% block content %}
Content
{{blogs.blog_content}}
{%else%}Something went wrong
{% endif %}{{c.comment_description}}
{% if user%} {%for u in user%} {% if c.user_id == u.id%}Something went wrong or there are no comments available for this blog post
{% endif %}


{{person.address}}
{{person.email}}
{{person.tel}}
Front-end Developer
Project Manager
Web & Software
Position: Project Manager
Description: {{person.experiences[0].description}}
I manage a team consisting of 12 employees and 6-10 highly skilled contractors. We develop website's for our own internal CMS including Shopify and WordPress.
Position: Project Manager & Front-end Developer
Description: {{person.experiences[1].description}}
I am one of the top developers in the RapidWeaver market where I have over 70 top selling addons and my latest work is featured as a built-in theme in their latest version (6).
Position: System Administrator
Description: {{person.experiences[2].description}}
During college I was a full-time volunteer here where our aim was to help "Prepare urban fatherless young men for life" and I helped in building the company from the ground up.
Position: Administration
Description: {{person.experiences[3].description}}
Developed a tracking database for logistical transportation convoy movements - used for creating accurate predictive re-deployment supply dates.
User Interface (UI) design, custom WP Admin design, custom WP theme design, Dashboard & Email Mktg dashboard design.
2014Custom WP theme changes & custom Google Maps polygon coordinate tool used for real estate drill-down navigation design.
2014Various custom PHP & WP projects: CaliforniaCraneSchool.com, CraneAccidents.com, CraneHunter.org, and more to come.
2011 - 2014Additions & changes to various DOM elements & stylesheets within company portal.2010


/etc/network/interfaces - network interface configuration for ifup and ifdown
/etc/network/interfaces contains network interface configuration information for
the ifup(8) and ifdown(8) commands. This is where you configure
how your system is connected to the network.
The following example configures two network interfaces: eth0 is brought up at
boot, and uses DHCP for IPv4 and SLAAC for IPv6, whereas eth1 is brought up
whenever the network hardware is detected, and is configured with static IPv4
and IPv6 addresses.
auto eth0
allow-hotplug eth1
iface eth0 inet dhcp
iface eth0 inet6 auto
iface eth1 inet static
address <IP_ADDRESS>/24
gateway <IP_ADDRESS>
iface eth1 inet6 static
address fec0:0:0:1::2/64
gateway fec0:0:0:1::1
Lines starting with `#' are ignored. Note that end-of-line comments are NOT
supported, comments must be on a line of their own.
A line may be extended across multiple lines by making the last
character a backslash.
The file consists of zero or more "iface",
"mapping", "auto", "allow-",
"rename", "source" and "source-directory"
stanzas. These will be described in more detail in the following
sections.
Lines beginning with the word "auto" are used to identify the physical
interfaces to be brought up when ifup is run with the -a option.
(This option is also used by the system boot scripts, so interfaces marked
"auto" are brought up at boot time.) Physical interface names should
follow the word "auto" on the same line. There can be multiple
"auto" stanzas. ifup brings the named interfaces up in the
order listed.
Lines beginning with "allow-" are used to identify
interfaces that should be brought up automatically by various subsystems.
This may be done using a command such as "ifup --allow=hotplug eth0
eth1", which will only bring up eth0 or eth1 if it is listed in an
"allow-hotplug" line. Note that "allow-auto" and
"auto" are synonyms. (Interfaces marked "allow-hotplug"
are brought up when udev detects them. This can either be during boot if the
interface is already present, or at a later time, for example when plugging
in a USB network card. Please note that this does not have anything to do
with detecting a network cable being plugged in.)
Lines beginning with "no-auto-down" are used to identify
interfaces that should not be brought down by the command "ifdown
-a". Its main use is to prevent an interface from being brought down
during system shutdown time, for example if the root filesystem is a network
filesystem and the interface should stay up until the very end. Note that
you can still bring down the interface by specifying the interface name
explicitly.
Lines beginning with "no-scripts" are used to identify
interfaces for which scripts in /etc/network/if-*.d/ should not be
run when those interfaces are brought up or down. he above will match eth0
and eth1, and will bring up both interfaces using the "iface eth"
stanza.
Lines beginning with "rename" are used to rename interfaces. It takes
one or more arguments in the form of "CUR=NEW", where CUR is the
name of an existing interface, and NEW is the new name. This becomes very
powerful when combined with pattern matching for the CUR interface.
Interfaces are renamed whenever "ifup" is called.
Renaming logically happens before anything else is done. So if an interface
is started with the name "foo", and it has to be renamed to
"bar" and brought up at boot time, then one should use the
following /etc/network/interfaces file:
rename foo=bar
auto bar
iface bar ...
However, if the interface is not renamed yet, it is possible to
use both "ifup foo" and "ifup bar". The former command
will then automatically be converted to the latter. This is mainly useful
when ifup is called automatically whenever an interface is hotplugged.
Interface renaming only works if the operating system supports it,
if an interface is not renamed to another existing interface, and may
require that the interface that is to be renamed has not been brought up
yet. If ifup tries to rename an interface and it fails, it will exit with an
error.
Lines beginning with "source" are used to include stanzas from other
files, so configuration can be split into many files. The word
"source" is followed by the path of file to be sourced. Shell
wildcards can be used. (See wordexp(3) for details.)
Similarly, "source-directory" keyword is used to source
multiple files at once, without specifying them individually or using shell
globs. Additionally, when "source-directory" is used, names of the
files are checked to match the following regular expression:
^[a-zA-Z0-9_-]+$. In other words, the names must consist entirely of
ASCII upper- and lower-case letters, ASCII digits, ASCII underscores, and
ASCII minus-hyphens. In the directory path, shell wildcards may be used as
well.
When sourcing files or directories, if a path doesn't have a
leading slash, it's considered relative to the directory containing the file
in which the keyword is placed. In the example above, if the file is located
at /etc/network/interfaces, paths to the included files are
understood to be under /etc/network.
By default, on a freshly installed Debian system, the interfaces
file includes a line to source files in the /etc/network/interfaces.d
directory.
Stanzas beginning with the word "mapping" are used to determine how a
logical interface name is chosen for a physical interface that is to be
brought up. The first line of a mapping stanza consists of the word
"mapping" followed by a pattern in shell glob syntax. Each mapping
stanza must contain a script definition. The named script is run with
the physical interface name as its argument and with the contents of all
following "map" lines (without the leading "map")
in the stanza provided to it on its standard input. The script must print a
string on its standard output before exiting. See
/usr/share/doc/ifupdown/examples for examples of what the script must
print.
Mapping a name consists of searching the remaining mapping
patterns and running the script corresponding to the first match; the script
outputs the name to which the original is mapped.
ifup is normally given a physical interface name as its
first non-option argument. ifup also uses this name as the initial
logical name for the interface unless it is accompanied by a suffix of the
form =LOGICAL, in which case ifup chooses LOGICAL as the
initial logical name for the interface. It then maps this name, possibly
more than once according to successive mapping specifications, until no
further mappings are possible. If the resulting name is the name of some
defined logical interface then ifup attempts to bring up the physical
interface as that logical interface. Otherwise ifup exits with an
error.
Stanzas defining logical interfaces start with a line consisting of the word
"iface" followed by the name of the logical interface. In simple
configurations without mapping stanzas this name should simply be the name of
the physical interface to which it is to be applied. (The default mapping
script is, in effect, the echo command.) The interface name is followed
by the name of the address family that the interface uses. This will be
"inet" for TCP/IP networking, but there is also some support for IPX
networking ("ipx"), and IPv6 networking ("inet6").
Following that is the name of the method used to configure the interface.
Additional options can be given on subsequent lines in the stanza.
Which options are available depends on the family and method, as described
below. Additional options can be made available by other Debian packages.
For example, the wireless-tools package makes available a number of options
prefixed with "wireless-" which can be used to configure the
interface using iwconfig(8). (See wireless(7) for
details.) A list of packages providing additional options is mentioned in
the section "OPTIONS PROVIDED BY OTHER PACKAGE".
Options are usually indented for clarity (as in the example above)
but are not required to be.
Multiple "iface" stanzas can be given for the same
interface, in which case all of the configured addresses and options for
that interface will be applied when bringing up that interface. This is
useful to configure both IPv4 and IPv6 addresses on the same interface
(although if no inet6 stanza is present, the kernel will normally still
perform stateless address autoconfiguration if there is an IPv6 route
advertisement daemon on the network). It can also be used to configure
multiple addresses of the same type on a single interface.
It is possible to define interface definition templates and extend them using
the inherits keyword:
iface ethernet inet static
mtu 1500
hwaddress 11:22:33:44:55:66
iface eth0 inet static inherits ethernet
address <IP_ADDRESS>/24
This may be useful to separate link-level settings shared by
multiple interfaces from, for example, IP address settings specific to every
interface.
It is possible to use patterns to match one or more real interfaces. These
patterns can currently appear in lines beginning with "auto",
"allow-", "rename" and on the command line. A pattern has
the following format (see below for exceptions for GNU/Hurd):
[VARIABLE]/VALUE[/[OPTIONS]][=LOGICAL]
If no VARIABLE is given, this pattern will match interface names
against the given VALUE. VALUE can contain wildcard patterns such as ? and
*, see the fnmatch(3) function. When ifup or ifdown is
run, patterns are replaces by all real interfaces that are currently known
to the operating system kernel and whose names match the pattern. For
example, given the following line:
auto /eth*
If the kernel knows about the interfaces with names lo, eth0 and
eth1, then the above line is then interpreted as:
auto eth0 eth1
Note that there must still be valid "iface" stanzas for
each matching interface. However, it is possible to combine a pattern with a
mapping to a logical interface, like so:
auto /eth*=eth
iface eth inet dhcp
Valid variable names are "mac", in which case value is
matched against the interface's MAC address. On Linux, the variable name can
also be any filename in /sys/class/net/<iface>/, in which case the
value is matched against the contents of the corresponding file.
The OPTIONS field currently only supports a number. If given, only
the n-th interface that has a matching value will actually be used, where n
is the number given, starting at 1. So /eth*/1 will match the first
interface whose name starts with eth.
On GNU/Hurd, interface names start with /dev/, and this obviously
clashes with the format for patterns. To ensure an interface name like
/dev/eth0 does not get interpreted as a pattern, any pattern that starts
with /dev/ is ignored, and instead interpreted as a literal interface name.
To make a pattern that matches interface names on GNU/Hurd, use something
like:
auto /?dev?eth*=eth
iface eth inet dhcp
To ease the configuration of VLAN interfaces, interfaces having . (full
stop character) in the name are configured as 802.1q tagged virtual LAN
interface. For example, interface eth0.1 is a virtual interface with
VLAN ID 1 having eth0 as its parent interface.
VLAN interfaces are mostly treated as independent interfaces. As
such, a VLAN interface is normally not automatically brought up when its
parent interface is brought up. The exception is when ifup is called with
the --allow option, in which case all VLAN interfaces that are in the same
allow class as the parent interface are brought up together with the parent
interface. For example:
allow-hotplug eth0 eth0.1
iface eth0 inet static
address ...
iface eth0.1 inet static
address ...
iface eth0.2 inet static
address ...
In the above example, when "ifup --allow hotplug eth0"
is called (either manually or because udev triggers this when a network
device is hotplugged), the interface eth0 and the VLAN interface eth0.1 are
brought up, but eth0.2 is not.
Keep in mind that pattern matching will only match interfaces the
kernel knows about, so it is not possible to specify "auto
/eth0.*" and have all VLAN interfaces for eth0 be brought up at boot
time. Another way to ensure that a VLAN interface is brought up
automatically when the parent interface is brought up, is to use a recursive
call to ifup, like so:
iface eth0 inet manual
up ifup eth0.3
iface eth0.3 inet static
address ...
Note that there is no need to add an explicit call to ifdown,
since VLAN interfaces are automatically brought down whenever their parent
interfaces are brought down.
The following "command" options are available for every family and
method. Each of these options can be given multiple times in a single stanza,
in which case the commands are executed in the order in which they appear in
the stanza. (You can ensure a command never fails by suffixing them with
"|| true".)
- pre-up command
- Run command before bringing the interface up. If this command fails
then ifup aborts, refraining from marking the interface as
configured, prints an error message, and exits with status 0. This
behavior may change in the future.
- up command
- post-up command
- Run command after bringing the interface up. If this command fails
then ifup aborts, refraining from marking the interface as
configured (even though it has really been configured), prints an error
message, and exits with status 0. This behavior may change in the
future.
- down command
- pre-down command
- Run command before taking the interface down. If this command fails
then ifdown aborts, marks the interface as deconfigured (even
though it has not really been deconfigured), and exits with status 0. This
behavior may change in the future.
- post-down command
- Run command after taking the interface down. If this command fails
then ifdown aborts, marks the interface as deconfigured, and exits
with status 0. This behavior may change in the future.
- description name
- Alias interface by name
There are four directories in which scripts can be placed which will always be
run for any interface during certain phases of ifup and ifdown commands. These
are:
- /etc/network/if-pre-up.d/
- Scripts in this directory are run before bringing the interface up.
- /etc/network/if-up.d/
- Scripts in this directory are run after bringing the interface up.
- /etc/network/if-down.d/
- Scripts in this directory are run before bringing the interface down.
- /etc/network/if-post-down.d/
- Scripts in this directory are run after bringing the interface down.
The scripts in which are run (with no arguments) using
run-parts(8) after the corresponding pre-up, up,
down and post-down options in the
/etc/network/interfaces file itself have been processed. Please note
that as post-up and pre-down are aliases, no files in the
corresponding directories are processed. Please use if-up.d and
if-down.d directories instead.
All hook scripts, and the commands executed by pre-up, up,
post-up, pre-down, down and post-down have access
to the following environment variables:
- IFACE
- The physical name of the interface being processed, or "--all"
(see below).
- LOGICAL
- The logical name of the interface being processed, or "auto"
(see below).
- ADDRFAM
- The address family of the interface, or "meta" (see below).
- METHOD
- The method of the interface (e.g., static), or "none"
(see below).
- CLASS
- The class of interfaces being processed. This is a copy of the value given
to the --allow option when running ifup or ifdown, otherwise it is
set to "auto" when the --all option is used.
- MODE
- start if run from ifup, stop if run from ifdown.
- PHASE
- As per MODE, but with finer granularity, distinguishing the pre-up,
post-up, pre-down and post-down phases.
- VERBOSITY
- Indicates whether --verbose was used; set to 1 if so, 0 if
not.
- PATH
- The command search path:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Additionally, all options given in an interface definition stanza
are exported to the environment in upper case with "IF_" prepended
and with hyphens converted to underscores and non-alphanumeric characters
discarded.
When ifupdown is being called with the --all option, before
doing anything to interfaces, it calls all the hook scripts (pre-up
or down) with IFACE set to "--all", LOGICAL
set to the current value of --allow parameter (or "auto" if it's
not set), ADDRFAM="meta" and
METHOD="none". After all the interfaces have been brought
up or taken down, the appropriate scripts (up or post-down)
are executed.
Ifupdown uses per-interface locking to ensure that concurrent ifup and ifdown
calls to the same interface are run in serial. However, calls to different
interfaces will be able to run in parallel. It is therefore important that any
hook scripts and pre-up, up, down and post-down
commands are written with the possibility of parallel execution in mind.
It is allowed to recursively call ifup and ifdown
from hook scripts and interface commands, as long as these calls refer to a
different interface than the one that is already being (de)configured. Loops
are detected and will result in the call failing instead of a deadlock,
although it is best if one does not rely on that.
This manual page documents the configuration options provided by the ifupdown
package. However, other packages can make other options available for use in
/etc/network/interfaces. Here is a list of packages that provide such
extensions:
arping, avahi-autoipd, avahi-daemon, bind9, bridge-utils,
clamav-freshclam, controlaula, epoptes-client, ethtool, guidedog,
hostap-utils, hostapd, htpdate, ifenslave, ifmetric, ifupdown-extra,
ifupdown-multi, ifupdown-scripts-zg2, initscripts, isatapd, linux-wlan-ng,
lprng, macchanger, miredo, nslcd, ntpdate, openntpd, openresolv,
openssh-server, openvpn, openvswitch-switch, postfix, resolvconf,
sendmail-base, shorewall-init, slrn, slrnpull, tinc, ucarp, uml-utilities,
uruk, vde2, vlan, vzctl, whereami, wide-dhcpv6-client, wireless-tools,
wpasupplicant.
Please consult the documentation of those packages for information
about how they extend ifupdown.
This section documents the methods available in the inet address family.
This method may be used to define the IPv4 loopback interface.
Options
This method may be used to define Ethernet interfaces with statically allocated
IPv4 addresses.
Options
- address address
- Address (dotted quad/netmask) required
- netmask mask
- Netmask (dotted quad or number of bits) deprecated
- broadcast broadcast_address
- Broadcast address (dotted quad, + or -) deprecated. Default value:
"+"
- metric metric
- Routing metric for default gateway (integer)
- gateway address
- Default gateway (dotted quad)
- pointopoint address
- Address of other end point (dotted quad). Note the spelling of
"point-to".
- hwaddress address
- Link local address or "random".
- mtu size
- MTU size
- scope
- Address validity scope. Possible values: global, link, host
This method may be used to define interfaces for which no configuration is done
by default. Such interfaces can be configured manually by means of up
and down commands or /etc/network/if-*.d scripts.
Options
- hwaddress address
- Link local address or "random".
- mtu size
- MTU size
This method may be used to obtain an address via DHCP with any of the tools:
dhclient, pump, udhcpc, dhcpcd. (They have been listed in their order of
precedence.) If you have a complicated DHCP setup you should note that some of
these clients use their own configuration files and do not obtain their
configuration information via ifup.
Options
- hostname hostname
- Hostname to be requested (pump, dhcpcd, udhcpc)
- metric metric
- Metric for added routes (dhclient)
- leasehours leasehours
- Preferred lease time in hours (pump)
- leasetime leasetime
- Preferred lease time in seconds (dhcpcd)
- vendor vendor
- Vendor class identifier (dhcpcd)
- client client
- Client identifier (dhcpcd)
- hwaddress address
- Hardware address.
This method may be used to obtain an address via bootp.
Options
- bootfile file
- Tell the server to use file as the bootfile.
- server address
- Use the IP address address to communicate with the server.
- hwaddr addr
- Use addr as the hardware address instead of whatever it really
is.
This method is used to create GRE or IPIP tunnels. You need to have the
ip binary from the iproute package. For GRE tunnels, you will
need to load the ip_gre module and the ipip module for IPIP tunnels.
Options
- address address
- Local address (dotted quad) required
- mode type
- Tunnel type (either GRE or IPIP) required
- endpoint address
- Address of other tunnel endpoint required
- dstaddr address
- Remote address (remote address inside tunnel)
- local address
- Address of the local endpoint
- metric metric
- Routing metric for default gateway (integer)
- gateway address
- Default gateway
- ttl time
- TTL setting
- mtu size
- MTU size
This method uses pon/poff to configure a PPP interface. See those commands for
details.
Options
- provider name
- Use name as the provider (from /etc/ppp/peers).
- unit number
- Use number as the ppp unit number.
- options string
- Pass string as additional options to pon.
This method uses wvdial to configure a PPP interface. See that command for more
details.
Options
- provider name
- Use name as the provider (from /etc/wvdial.conf).
This method uses avahi-autoipd to configure an interface with an IPv4 Link-Layer
address (<IP_ADDRESS>/16 family). This method is also known as APIPA or IPAC,
and often colloquially referred to as "Zeroconf address".
Options
This section documents the methods available in the ipx address family.
This method may be used to setup an IPX interface. It requires the
ipx_interface command.
Options
- frame type
- type of Ethernet frames to use (e.g. 802.2)
- netnum id
- Network number
This method may be used to setup an IPX interface dynamically.
Options
- frame type
- type of Ethernet frames to use (e.g. 802.2)
This section documents the methods available in the inet6 address family.
This method may be used to define interfaces with automatically assigned IPv6
addresses. Using this method on its own doesn't mean that RDNSS options will
be applied, too. To make this happen, rdnssd daemon must be installed,
properly configured and running. If stateless DHCPv6 support is turned on,
then additional network configuration parameters such as DNS and NTP servers
will be retrieved from a DHCP server. Please note that on ifdown, the lease is
not currently released (a known bug).
Options
- privext int
- Privacy extensions (RFC4941) (0=off, 1=assign, 2=prefer)
- accept_ra int
- Accept router advertisements (0=off, 1=on, 2=on+forwarding). Default
value: "2"
- dhcp int
- Use stateless DHCPv6 (0=off, 1=on)
- request_prefix int
- Request a prefix through DHCPv6 Prefix Delegation (0=off, 1=on). Default
value: "0"
- ll-attempts
- Number of attempts to wait for a link-local address. Default value:
"60"
- ll-interval
- Link-local address polling interval in seconds. Default value:
"0.1"
This method may be used to define the IPv6 loopback interface.
Options
This method may be used to define interfaces with statically assigned IPv6
addresses. By default, stateless autoconfiguration is disabled for this
interface.
Options
- address address
- Address (colon delimited/netmask) required
- netmask mask
- Netmask (number of bits, eg 64) deprecated
- metric metric
- Routing metric for default gateway (integer)
- gateway address
- Default gateway (colon delimited)
- media type
- Medium type, driver dependent
- hwaddress address
- Hardware address or "random"
- mtu size
- MTU size
- accept_ra int
- Accept router advertisements (0=off, 1=on, 2=on+forwarding)
- autoconf int
- Perform stateless autoconfiguration (0=off, 1=on). Default value:
"0"
- privext int
- Privacy extensions (RFC3041) (0=off, 1=assign, 2=prefer)
- scope
- Address validity scope. Possible values: global, site, link, host
- preferred-lifetime int
- Time that address remains preferred
- dad-attempts
- Number of attempts to settle DAD (0 to disable DAD). Default value:
"60"
- dad-interval
- DAD state polling interval in seconds. Default value: "0.1"
This method may be used to define interfaces for which no configuration is done
by default. Such interfaces can be configured manually by means of up
and down commands or /etc/network/if-*.d scripts.
Options
- hwaddress address
- Hardware address or "random"
- mtu size
- MTU size
This method may be used to obtain network interface configuration via stateful
DHCPv6 with dhclient. In stateful DHCPv6, the DHCP server is responsible for
assigning addresses to clients.
Options
- hwaddress address
- Hardware address or "random"
- accept_ra int
- Accept router advertisements (0=off, 1=on, 2=on+forwarding). Default
value: "1"
- autoconf int
- Perform stateless autoconfiguration (0=off, 1=on)
- request_prefix int
- Request a prefix through DHCPv6 Prefix Delegation (0=off, 1=on). Default
value: "0"
- ll-attempts
- Number of attempts to wait for a link-local address. Default value:
"60"
- ll-interval
- Link-local address polling interval in seconds. Default value:
"0.1"
This method may be used to setup an IPv6-over-IPv4 tunnel. It requires the
ip command from the iproute package.
Options
- address address
- Address (colon delimited/netmask) required
- netmask mask
- Netmask (number of bits, eg 64) deprecated
- endpoint address
- Address of other tunnel endpoint (IPv4 dotted quad) required
- local address
- Address of the local endpoint (IPv4 dotted quad)
- metric metric
- Routing metric for default gateway (integer)
- gateway address
- Default gateway (colon delimited)
- ttl time
- TTL setting
- mtu size
- MTU size
- preferred-lifetime int
- Time that address remains preferred
This method may be used to setup an 6to4 tunnel. It requires the ip
command from the iproute package.
Options
- local address
- Address of the local endpoint (IPv4 dotted quad) required
- metric metric
- Routing metric for default gateway (integer)
- ttl time
- TTL setting
- mtu size
- MTU size
- preferred-lifetime int
- Time that address remains preferred
This section documents the methods available in the can address family.
This method may be used to setup an Controller Area Network (CAN) interface. It
requires the the ip command from the iproute package.
Options
- bitrate bitrate
- bitrate (1..1000000) required
- samplepoint samplepoint
- sample point (0.000..0.999)
- loopback loopback
- loop back CAN Messages (on|off)
- listenonly listenonly
- listen only mode (on|off)
- triple triple
- activate triple sampling (on|off)
- oneshot oneshot
- one shot mode (on|off)
- berr berr
- activate berr reporting (on|off)
The ifup and ifdown programs work with so-called
"physical" interface names. These names are assigned to hardware by
the kernel. Unfortunately it can happen that the kernel assigns different
physical interface names to the same hardware at different times; for example,
what was called "eth0" last time you booted is now called
"eth1" and vice versa. This creates a problem if you want to
configure the interfaces appropriately. A way to deal with this problem is to
use mapping scripts that choose logical interface names according to the
properties of the interface hardware. See the get-mac-address.sh script
in the examples directory for an example of such a mapping script. See also
Debian bug #101728.
The ifupdown suite was written by Anthony Towns<EMAIL_ADDRESS>This manpage was contributed by Joey Hess<EMAIL_ADDRESS>ifup(8), ip(8), ifconfig(8), run-parts(8),
resolvconf(8).
For advice on configuring this package read the Network
Configuration chapter of the Debian Reference manual, available
at http://www.debian.org/doc/manuals/debian-reference/ch05.en.html or
in the debian-reference-en package.
Examples of how to set up interfaces can be found in
/usr/share/doc/ifupdown/examples/network-interfaces.gz.


Height (in cm):
Weight (in kg):
Under Weight = Less than 18.6
Normal Range = 18.6 and 24.9
Overweight = Greater than 24.9


ENCLOSINGCIRCLE find the minimum circle enclosing a set of points. CIRCLE = enclosingCircle(POINTS); compute cirlce CIRCLE=[xc yc r] which enclose all points POINTS given as an [Nx2] array. Rewritten from a file from Yazan Ahed<EMAIL_ADDRESS>which was rewritten from a Java applet by Shripad Thite : http://heyoka.cs.uiuc.edu/~thite/mincircle/ See also: circles2d, points2d, boxes2d --------- author : David Legland INRA - TPV URPOI - BIA IMASTE created the 07/07/2005.


--- layout: default title: Software Craftsman - 20 years ---
Take note that this site is on BETA Don't ask me when is it going live


AMAIZING PEOPLE ARE MAKING DESIGNS IN A FUN ENVIRONMENT
ABOUT US
When you work with us, you are part of a team of commited collaborators. All aspects of our software
development process are intergrated, interactive and agile.
Our approach unifies design, development and product management to create exceptional products.
We start each project by understanding your business goals, the user's needs and the product
requirements.
Then we help translate them into active and elegant solutions.
SERVICES
Before we sign a contract or write a line of code our team will spend the neccesary time needed to
understand your product vision.
The outcome of the scoping session is a proposal or high-level statementof work.
Based on your requirements, we can provide a complete offering or just the piece you need.
WHAT WE DO
DESIGN
DESIGN
Our design offers a full range of services including brand strategy,interaction and visual
designand user experience testing.Throughout your project,our designers create and implement visual design and work
flows,solicit user feedback and work with you to make sure what gets built is what is
needed.
DEVELOPMENT
DEVELOPMENT
All engineers are fluent in the latest enterprise,mobile and web development
technologies.
They collaborate with your team to write and improve code on a daily basis, using proven
practices
such
as
test-driven development and pair programming.
PRODUCT MANAGEMENT
PRODUCT MANAGEMENT
Planning and development is iterative.Because we are constantly coding and
testing,the
products
we build are ready to go live.
This iterative process allows for changes as bussiness requirements evolve.


Policy, planning and health management: the current understanding
Jairnilson Silva Paim; Carmen Fontes Teixeira
Instituto de Saúde Coletiva. Universidade Federal da Bahia. Salvador, BA, Brasil
ABSTRACT
This work provides a literature review of Policy, Planning and Health Management between 1974 and 2005. Information is presented from previous research and publications, incorporating the production contained within the LILACS database from the last five years. The emergence of studies in these sub-themes is described in an attempt to associate them with political circumstances, with particular emphasis on: the Sanitary Reform Process, the construction of the National Health System and the reorientation of health practices. The particularities of the production in this field are discussed and the need for historical and epistemological work in Brazil is emphasized. The practical challenges impose techno-scientific expertise and, primarily, socio-political militancy on individual and collective subjects.
Keywords: Health policy, history. Health policy, trends. Health planning, organization & administration. Health management.
INTRODUCTION
Conducting a review of Policy, Planning and Health Management (PP&HM) affords an excellent opportunity to reflect not only on its theoretical-conceptual development, but, primarily, to systematize tendencies in its production of publications and empirical investigations. Due to the constitutive link between the composition in the field of public health, the movement for the democratization of health and the proposal for Brazilian Sanitary Reform (BSR), the thematic area of PP&HM must be analyzed within such a historical perspective. Thus, it was by examining the relationship between scientific production and political circumstances to reconcile new relationships between the State and society that Donnângelo7 (1983) elaborated a pioneering study on collective health research in Brazil.
This is not to suggest that before the 1970s there had not existed production within this thematic area. The theses defended in the Faculdade de Saúde Pública of the Universidade de São Paulo and in the Escola Nacional de Saúde Pública, the articles published in the Revista de Saúde Pública, the critical texts of Carlos Gentile de Mello and Mário Magalhães da Silveira (among others), and the reports of experiences and reflections divulged in the old Revista do Serviço Especial de Saúde Pública, all attest to the interest of those Brazilians involved in the sanitary field to studies of health services. Books were also published, including "Fundamentos da Administração Sanitária" (Fundamentals of Sanitary Administration)13 by Dr. Bichat de Almeida Rodrigues.
This initial production was centered on sanitary administration and included, subsequently, health programming. Planning and policy were themes less covered and were limited to questions of budget, organization and sanitary legislation. Along with the critique of social medicine during the early 1970s and the development of social health sciences, it was possible for the emergent collective health to reconstitute the PP&HM in Brazil. In this aspect, the publication "Medicina e Sociedade" (Medicine and Society), of Donnângelo,6 is a landmark for its reconstitution. In studying the relationships between the State and medical assistance, Donnângelo broke away from the dominant lines of interpreting government intervention in health, be it through the tendency to rationalize or through the guarantee of the right to health. In searching the social class dynamic for an explanation for State action, a perspective arose for the development of studies in health policy, as well as alternative forms of thinking about institutions and, consequently, of planning and management.
Hence, the present article uses, as an initial historical reference for the analysis of scientific production in PP&HM, the circumstances that favored: the emergence of collective health, the creation of the Centro Brasileiro de Estudos de Saúde (Cebes - Brazilian Center for Health Studies) in 1976, the development of postgraduate courses, the founding of the Associação Brasileira de Pós-graduação em Saúde Coletiva (Abrasco - Brazilian Association of Collective Health Postgraduate Programs) in 1979, and the strengthening of the so-called sanitary movement. An attempt was made to characterize the development of this field, seeking to identify the trends that marked the production of knowledge in PP&HM, whilst considering changes in political and academic circumstances throughout this period.
Thus, the objective of this study was to evaluate the current knowledge of PP&HM in the field of collective health in Brazil between 1974 and 2005, seeking to contextualize the production and dissemination of knowledge during distinct periods. However, an evaluation of quantitative data was not attempted, nor was an exhaustive survey of the scientific production, as in previous works,2,3,9,16 since this was based on research of the Literatura Latino-Americana e do Caribe em Ciências da Saúde (LILACS - Latin-American and Caribbean Literature on Health Sciences) bibliographic database in the period from 2001 to 2005.
HEALTH POLICY
Health policy is understood to be the social response (in action or omission) of an organization (such as the State) in the face of the health conditions of individuals and populations, and their determinants as well as its relation to production, distribution, management and regulation of goods and services that affect human health and the environment. Health policy covers questions relating to power in health (Politics), as well as those that encompass the establishment of directives, plans and programs of health (Policy). Thus, the word policy, as is explicit in the Portuguese language, expresses both the dimensions of power and the directives. Despite this, as an academic area, health policy addresses the relations of power in the conformation of the agenda, and in the formulation, conduct, implementation and evaluation of policies.11 Thus, health policy involves studies on the role of the State, the relationship between the State and society, the reactions to health conditions and their determinants by the population, through proposals and priorities for public action. It also includes the study of its relationship to economic and social policies, social control, health economy and financing.9
In the origins of health policy research in Brazil are found theses and journals that stimulated and supported debates on the performance of the nascent sanitary movement, as the nature of this movement and the challenges of the Sanitary Reform became objects of academic studies that established bridges with society.8
With the development of the Cebes activities and with the organization of Abrasco, such articulations became more integrated. The text "Pelo Direito Universal à Saúde" (For the Universal Right to Health),1 released during the 8th National Conference on Health, embodies this nature by the importance that it held during that historical event. However, this political visibility obscured efforts to consolidate health policy as an academic discipline, directed toward scientific production and subject to theoretical and methodological rigor.
Such consolidation came about with the production of dissertations and postgraduate theses and of the first surveys and systematic publications during the second half of the 1990s.2,16 Thus, not only did broader studies on the State and public policies become more visible, but research was also focused on the implementation of policies in organizations.
In an investigation of the database of theses from the Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (Capes - Coordination for the Improvement of Higher Education Personnel) on health policy between 1993 and 1998, Ayres3 (2000) confirmed that the studies concentrated on the following topics: a) emergency processes, formulation and implementation of policies (constitution of the public agenda); b) dynamic and performance of the social actors (mobilization/demobilization); c) socio-historical context; d) life cycle of each policy (policy cycle); e) repercussions and recurring policy patterns; f) and questions that become objects of intervention.
Levcovitz et al9 (2003) considered in addition to theses and dissertations, books, journal articles (Brazilian and international), conferences and Brazilian meetings on health. The authors analyzed the political debate and the knowledge produced in PP&HM and adopted a timeline for the trends in Brazilian health policies divided into five stages.
The first (1974-1979) was characterized by the investigation of the economic, political and social determinants of the conformation of health systems and the formulation of alternatives. Notable among the themes covered are: the State and health policy; the National Health System; the welfare system; diagnosis of social and health conditions; and health programs.
The second (1980-1986) involved the dissemination of proposals for reform and socio-political cohesion. During this phase, themes appeared such as: increased coverage, history of psychiatry, medical practice, assistance model primary health care, reform principles, social movements, strategic planning, services diagnosis and specific programs (child, woman, and others).
The third phase (1987-1990) was characterized by the judicial/legal arrangement of principles and directives of the reform project. The following themes appeared in this phase: citizenship, epidemiological patterns and inequalities, financing, access and demand for services, decentralization, and others.
The fourth phase (1991-1998) sought to define the role of each sphere of government and the elaboration of instruments for this relationship, with the production of knowledge directed toward the following aspects: adjustment of State reform, "municipalization", the Programa Saúde da Família (PSF - Family Heath Program), public-private relations, promotion of health, districting/local health systems, social security, social control, assistance models, and others.
The final phase (1999-2000) analyzed by the authors addressed the regulation of financing and the organization of management models and attention to the regionalized services network. In this phase, scientific production concentrated upon the adjustment of State reform, financing, social control, assistance models and public-private relations. New themes also appeared, including: health economy, health and the environment, information systems, human resources management, technology and health, the work process, and others.
For the purposes of classification, a sixth phase can be included (2001-2005) to the aforementioned timeline. Even running the risk of oversimplification, it is worth noting in this phase the search for stability of financing (as required by the 29th constitutional amendment) and the development of basic care, such as the expansion of the PSF. Scientific production was concentrated on the Sistema Único de Saúde (SUS - National Health System) and the Sanitary Reform, with emphasis on human resources, social control, health information, decentralization, integrality and equity. Also notable was the expansion of health economy, which resulted from studies on the so-called "health maintenance organization sector (HMOs)", financing, allocation of resources and public-private relations. Thus, the segmentation of the health services system in Brazil among the public health system (SUS) and the market was quantitatively expressed in the production of the PP&HM.
Alongside these studies there was the strong presence of research on basic health care emphasizing family health. A dynamic scientific production appears on the promotion of health, mental health, oral health, care models, humanization and health care. During the period in question, the production of PP&HM also covered: medication policy and pharmaceutical assistance (emphasizing generic drugs), metropolitan health, sanitary vigilance, worker health and indigenous health. Health evaluation represents a theme frequently observed. General studies on the SUS and its implementation were seen in studies of organization and regionalization, special programs (AIDS, dengue, tuberculosis, hanseniasis, women, children, adolescents, aged and others) and hospital care. However, publications on macro- and micro-regulation of assistance, ethical aspects, and the health of the Black and male population are still rare.
Health Planning and Management
The planning analysis of scientific production in the present article included: studies on the implementation of a coordinated set of actions to achieve a determined objective; studies of the strategies used to confront problems and the mechanisms of policy implementation; theoretical and methodological studies for the construction of plans, programs and projects (planning in health, strategic planning and health programming). The management sub-theme included studies on the creation and utilization of means that substantiate the principles of political organization; and included services management studies and health systems, quality management, strategic management, human resources management, budget and financial management.9
From the timeline elaborated by the cited authors,9 the first phase (1974-1979) had as its principal characteristic the emergence of studies on the organization of community medical services, undertaking research on coverage and accessibility of the population to primary care services, critical testing, necessities of health and of services, community health diagnoses, evaluation of programs and others.
In the subsequent phase (1980-1986), studies appeared on programs for the extension of health cover that were elaborated and implemented in the previous period, initially experimentally and later as a strategy for institutional modernization in the field of public health, alongside studies of programs for education and personnel training and experiences of assistance-instructor integration.
The end of the 1980s (3rd phase) was marked by the elaboration and implementation of proposals for reform in management, planning and organization of services. Notable during this period was the growing interest for theoretical-methodological questions in the health planning and management field. The confronting of "practical challenges" was evidenced by academic instructors and researchers that came to be involved in the state and municipal health secretaries. These challenges stimulated reflections on questions relating to the change in political-management practices in the public sphere of the 4th phase (1991-1998) in various academic centers. This led to a diversification of theoretical-methodological themes and approaches, shaping various streams of thought, which were expressed in the production of books and articles that reflected the multidisciplinary nature of topics and approaches in the area. Indeed, between the 1980s and 1990s, historical and theoretical studies appeared on the conceptual and methodological development of health planning that emphasized the unfolding critique of the instrumental character of planning and its articulation with the process of reorientation of health policy. Also worth noting are reports of local experiences at the start of the regionalization process of health services in various Brazilian states and municipalities.
In phase 5 (1999-2000), studies analyzing and evaluating health management, in its various dimensions and levels of complexity, gained prominence. The decentralized management of the SUS became the background for the large set of studies on aspects relating to planning, programming, reorganization of the work process, health information systems, training of personnel, monitoring practices, supervision and evaluation of health systems and services, as well as studies on the participation and social control of the SUS.
Between 2001 and 2005 (phase 6), the most obvious direction of knowledge production in planning and management was the substantial increase of research on the "municipalization" of management and the expansion of basic health care. From the second half of the 1990s, some of these themes were consolidated in debates, such as the issues relating to the decentralized management of the SUS, as a result of advances in the decentralization process and the process of change in the health care model resulting from the implementation of the PSF. Presently, the production of information concerning hospital administration is increasing, probably as a result of the unfolding political-institutional circumstances in the areas of planning and management. This area has come to include themes critical of the process of change in the care model, such as the reorientation of policy and management of hospital units. An increase in studies and proposals in the areas of management information and health communication is also evident, addressing challenges posed to managers by the rapidly advancing technologies that reconcile the Internet and telecommunications with health practices.
FINAL CONSIDERATIONS
The literature review of the material concerning scientific production suggests that the PP&HM thematic area is more directed toward intervention than investigation, despite recent efforts of research groups. This does not suggest that its topics are outside the sphere of scientific rigor. However, because they border on the immediacy of practice, these tend to be intertwined within diverse ideologies.10
In the scientific field, symbolic power5 is expressed in recognition, prestige, titles, honors and fame but it is also in conflict with economic and administrative power in regards to access to resources, infrastructure and financing mechanisms for research. The political nature of this field, and of the process of knowledge production, must be evaluated so that the need for objectivity in research problems and the search for objectivity with the supposed scientific neutrality are not confused. Thus, it is impossible to ignore values, beliefs and ideologies, but nevertheless the theoretical-methodological rigor in critiques and in the production of evidence should not be discarded.
Thus, it is worth understanding scientific practice as a field where knowledge and symbols are produced, in which the understanding of information and knowledge as public goods should be valued. Socially distributed knowledge12 should also be valued and there must be a search for "the elaboration of health policies and actions that have better chances of being effective and bring greater benefits for the health of the population".4
The PP&HM area, in the context of collective health, expresses most clearly the two dimensions (knowledge and practices) of the field, i.e. the fact that the knowledge produced answers the problems and challenges posed to it by subjects in their political action in determined historical contexts. This presupposition allows for the understanding of the direction of scientific research in this area, while the selection of themes, the delimitation of problems, the choice of certain theoretical-methodological approaches and even the dissemination of results, reveal a complex web of relationships between academia and services institutions. Such relationships are mediated by agencies that further research and by the collective health community. Thus, the PP&HM thematic area, founded upon social and human sciences, presents certain specificities and has distinct implications, be they in technological incorporation or in socio-political militancy.17
This thematic area is significantly complicated, such that there are moments when information is lacking for decision-making, and others when there is sufficient knowledge but the decisions are delayed, and others still where the decisions are necessary even in the face of few data. An example of this is the precaution principle in sanitary vigilance and environmental health. Thus, "the process of transforming knowledge into evidence that can sustain a decision is complex and never totally scientific, being permeated by different interpretations and values of existing knowledge, in the same manner that the process of knowledge production and dissemination is mediated by relations that are established within the scientific community and between the scientific community and the various sectors of societal interests".4
With regards to health policy, the majority of studies undertaken until the beginning of the 1990s presented a macro perspective, and rarely referred to health services and institutions. Studies based on broad categories, such as State, means of production, social training and others, did not use more specific concepts that reflected the particular realities and that allowed for certain interventions between the singular, the particular and the general.10 Subsequently, an increase was evident in the area with the development of investigations on policies, institutions and health practices, in addition to the increase in studies evaluating health.2,16 Presently, it is notable that there is a growing preoccupation with the evaluation of public policies. During 2005, the following were examples of this: the seminar on the "Effectiveness of Policies Promoting Health" (Rio de Janeiro), the significant presence of this theme in the 3rd Brazilian Congress of Social and Human Health Sciences of Abrasco (Florianópolis), the launching of books and of the supplement to the Cadernos de Saúde Pública18 dedicated to the "Investigation and Evaluation of Health Services". It is also worth noting that the most influential directions for health policy were, on the one hand, the extension of investigation topics (health economy, heath promotion, mental health, care and subjectivity, among others) and, on the other, the diversification of theoretical-methodological approaches.
The directions characteristics of planning and management are the diversification of approaches and, especially, the development of theoretical-conceptual studies in technology proposals. Such proposals have spread in institutional practice, generating many reports, case studies and evaluative studies. The development of these proposals has pointed to the centrality of the subject of practices,19 that is, of health managers and workers, in addition to the actual population represented in the health councils.
However, the PP&HM has not been the target of systematic studies concerning its topics, methods and techniques in a historical and epistemological perspective.14 The interface between theory and practice, generated by the epistemological critique and by experimentation with methods and techniques, marks the singularity of this area. This is characterized by the search for "technological development" that mediates the concepts, methods and instruments with the action of concrete subjects in the area of health organizations, addressing intervention on problems, necessities and political demands on health.
Thus, some theoretical contributions15,17 already available could constitute a starting point for more detailed historic and epistemological work in PP&HM. Still, it is the challenges of practice, particularly in underdeveloped, dependent and peripheral capitalist countries, that impose socio-political militancy and techno-scientific ability on their subjects, individuals and collectives.
REFERÊNCIAS


This is the main worker class for the executor pipeline, which handles
loading an action plugin to actually dispatch the task to a given host.
This class roughly corresponds to the old Runner() class.
|
|
__init__(self,
host,
task,
job_vars,
play_context,
new_stdin,
loader,
shared_loader_obj,
rslt_q)
x.__init__(...) initializes x; see help(type(x)) for signature |
source code
|
|
|
|
run(self)
The main executor entrypoint, where we determine if the specified
task requires looping and either runs the task with self._run_loop()
or self._execute(). |
source code
|
|
|
|
_get_loop_items(self)
Loads a lookup plugin to handle the with_* portion of a task (if
specified), and returns the items result. |
source code
|
|
|
|
_run_loop(self,
items)
Runs the task with the loop items specified and collates the result
into an array named 'results' which is inserted into the final result
along with the item for which the loop ran. |
source code
|
|
|
|
_squash_items(self,
items,
loop_var,
variables)
Squash items down to a comma-separated list for certain modules which
support it (typically package management modules). |
source code
|
|
|
|
_execute(self,
variables=None)
The primary workhorse of the executor system, this runs the task on
the specified host (which may be the delegated_to host) and handles
the retry/until and block rescue/always execution |
source code
|
|
|
|
_poll_async_result(self,
result,
templar)
Polls for the specified JID to be complete |
source code
|
|
|
|
_get_connection(self,
variables,
templar)
Reads the connection property for the host, and returns the correct
connection object from the list of connection plugins |
source code
|
|
|
|
_get_action_handler(self,
connection,
templar)
Returns the correct action plugin to handle the requestion task
action |
source code
|
|
|
Inherited from object :
__delattr__ ,
__format__ ,
__getattribute__ ,
__hash__ ,
__new__ ,
__reduce__ ,
__reduce_ex__ ,
__repr__ ,
__setattr__ ,
__sizeof__ ,
__str__ ,
__subclasshook__
|


DfE enquiries
Central newsdesk 020 7783 8300
General enquiries 0370 000 2288
News story
Information on the number of schools to have applied for academy status.
The Secretary of State has outlined the number of schools which have shown an interest in becoming academies following the Department for Education announcement of the intention to expand the programme.
Regarding the schools that have shown an interest in becoming academies, Secretary of State for Education Michael Gove said:
I believe that headteachers and teachers know best how to run schools, not local bureaucrats or politicians. That’s why last week I wrote to every school in the country inviting them to take up academy freedoms if they wished to do so. The response has been overwhelming. In just 1 week, over 1,100 schools have applied. Of these, 626 are outstanding schools, including over 250 primary schools, nearly 300 secondary schools (over half of all the outstanding secondary schools in the country) and over 50 special schools.
Total number of schools who have applied for academy freedoms: 1,114
Of the outstanding schools that have applied:
Central newsdesk 020 7783 8300
General enquiries 0370 000 2288
Published: 2 June 2010


wifi: AllovueGHQ
password: baltimorebreakfast
Jason
Hyien
Olivia
Jose
Sal
Eric (me)
What's the name of Allovue's latest JS framework?
allo-vue.js
When you act like I'm inconveniencing you
"No problem if you've been busy, but wanted to find time to discuss how we can connect your products to mobile apps"
Unsubscribe buttons
Unsubscribe buttons
When you can't take a hint...
Hey Eric, would you like to use our product?
Hey Eric, just wanted to follow up...
Hey Eric, just wanted to check in again. Did you forget about me?
Hey Eric, PLEASE USE MY SERVICE. PLEASSSSEEE
When your had one job to do...
${you_name_here}, just wanted to connect about ${job_opportunity_here}