Check-in [af15659622]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Edit several www/*.wiki files to include directory location and operating-system command prompt character and to make several other minor changes.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:af156596225bc49f47081b4db6061b3b8da0edeb
User & Date: mrh 2015-06-15 19:40:38
Context
2015-06-15
21:53
Edit www/download.wiki to recommend download expand in home directory and to add instructions on creating empty ~/.pylintrc file. check-in: 42f017f7fe user: mrh tags: trunk
19:40
Edit several www/*.wiki files to include directory location and operating-system command prompt character and to make several other minor changes. check-in: af15659622 user: mrh tags: trunk
18:28
Add www/license.wiki that contains MIT license and add link to that page in the www/contents.wiki file. check-in: b6debef099 user: mrh tags: trunk
Changes

Changes to www/cloningrepo.wiki.

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
..
32
33
34
35
36
37
38
39

<b>Installing Fossil</b>

Fossil is a free, open-source distributed software configuration
management system described [http://www.fossil-scm.org|here].
Installing Fossil involves downloading a single executable file to
your computer and putting it in a directory that is on your PATH.  The
latest versions of Fossil are available
[http://www.fossil-scm.org/download.html|here] and the "Fossil Quick
Start" document is available
[http://www.fossil-scm.org/fossil/doc/trunk/www/quickstart.wiki|here].
Test your Fossil installation by changing to any directory other than
the one in which you put the Fossil executable and then entering the
following command at the operating system prompt:

<tt>fossil version</tt>

If the installation has been successful, Fossil will write to the
screen a message something like this:

<tt>This is fossil version 1.32 <nowiki>[6c40678e91]</nowiki>
2015-03-14 13:20:34 UTC</tt>

................................................................................
<b>Cloning the OSPC-ACA Repository</b>

Text goes here.

<b>Checking Out a Local Source-Code Tree</b>

Text goes here.








|







|







 







<
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
..
32
33
34
35
36
37
38


<b>Installing Fossil</b>

Fossil is a free, open-source distributed software configuration
management system described [http://www.fossil-scm.org|here].
Installing Fossil involves downloading a single executable file to
your computer and putting it in a directory that is on your PATH.  The
latest versions of Fossil for Windows, Mac, and Linux, are available
[http://www.fossil-scm.org/download.html|here] and the "Fossil Quick
Start" document is available
[http://www.fossil-scm.org/fossil/doc/trunk/www/quickstart.wiki|here].
Test your Fossil installation by changing to any directory other than
the one in which you put the Fossil executable and then entering the
following command at the operating system prompt:

<tt><any-dir-not-containing-fossil-executable>$ fossil version</tt>

If the installation has been successful, Fossil will write to the
screen a message something like this:

<tt>This is fossil version 1.32 <nowiki>[6c40678e91]</nowiki>
2015-03-14 13:20:34 UTC</tt>

................................................................................
<b>Cloning the OSPC-ACA Repository</b>

Text goes here.

<b>Checking Out a Local Source-Code Tree</b>

Text goes here.

Changes to www/contents.wiki.

8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
<li> [./policy.wiki|How to Specify Your Own Policy Input Files] </li>
<li> [./statedata.wiki|Historical State Data] </li>
<li> [./validation.wiki|Project Validation] </li>
</ul>

<br>

<h2>Developer Documents:</h2>
<ul>
<li> [./cloningrepo.wiki|Cloning Project Repository] </li>
<li> [./changingcode.wiki|Making Code Changes] </li>
<li> [./sharingcode.wiki|Sharing Code Changes] </li>
</ul>

<br>







|







8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
<li> [./policy.wiki|How to Specify Your Own Policy Input Files] </li>
<li> [./statedata.wiki|Historical State Data] </li>
<li> [./validation.wiki|Project Validation] </li>
</ul>

<br>

<h2>Contributor Documents:</h2>
<ul>
<li> [./cloningrepo.wiki|Cloning Project Repository] </li>
<li> [./changingcode.wiki|Making Code Changes] </li>
<li> [./sharingcode.wiki|Sharing Code Changes] </li>
</ul>

<br>

Changes to www/download.wiki.

31
32
33
34
35
36
37

38

39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
the 2.7 version or the 3.4 version --- available from Continuum
Analytics at [http://store.continuum.io/cshop/anaconda|this link].
This installation will not interfere with any other Python installation
on your computer and does not require administrative privileges.

To check that the Python installation is working as expected, change
directory to <em>OSPC-ACA-<version></em> and at the operating-system

command prompt in that directory, enter the following command:


<tt>python --version</tt>

Your should see something like the following if you installed Python
2.7:

<tt>Python 2.7.9 :: Anaconda 2.2.0 (x86_64)</tt>

or like the following if you installed Python 3.4:

<tt>Python 3.4.3 :: Anaconda 2.2.0 (x86_64)</tt>

And finally, you need to install one Python package that is required
for the OSPC-ACA project that is not part of the Anaconda
distribution.  Do that by entering the following command:


<tt>python install_pylint.py</tt>

If you elect to read the Developer Documents later, you will learn
about how the pylint source-code checker is used in the OSPC-ACA
project.  But, at this point, there is no reason to learn more.

<b>Using Python to Execute Source Code</b>

To check that everything is working as expected, change directory
to <em>OSPC-ACA-<version></em> and at the operating-system command
prompt in that directory, enter the following command:

<tt>python tests.py</tt>

If Python is correctly installed and the project files have been
downloaded successfully, the tests.py script should execute in less
than a minute without writing any output to the screen.  If you
have a problem, please use [/reportlist|this link] to create a new
ticket that describes your problem.

If you pass the tests, begin exploring the <tt>ptc.py</tt> script by
entering the following commands for information:

<tt>python ptc.py --help</tt><br>
<tt>python ptc.py --sample_format</tt><br>
<tt>python ptc.py --output_format</tt>

and by entering the following command to see the script in action:

<tt>python ptc.py</tt>

Next read about how to create your own [./sample.wiki|sample files].







>
|
>

|












|
>

|

|









|










|
|
|



|


31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
the 2.7 version or the 3.4 version --- available from Continuum
Analytics at [http://store.continuum.io/cshop/anaconda|this link].
This installation will not interfere with any other Python installation
on your computer and does not require administrative privileges.

To check that the Python installation is working as expected, change
directory to <em>OSPC-ACA-<version></em> and at the operating-system
command prompt (typically either <tt>$</tt> or <tt>></tt>) in that
directory, enter the following command (that is, the text to the right
of the operating-system prompt):

<tt>OSPC-ACA-<version>$ python --version</tt>

Your should see something like the following if you installed Python
2.7:

<tt>Python 2.7.9 :: Anaconda 2.2.0 (x86_64)</tt>

or like the following if you installed Python 3.4:

<tt>Python 3.4.3 :: Anaconda 2.2.0 (x86_64)</tt>

And finally, you need to install one Python package that is required
for the OSPC-ACA project that is not part of the Anaconda
distribution.  Do that by entering the following command from the
OSPC-ACA-<version> directory:

<tt>OSPC-ACA-<version>$ python install_pylint.py</tt>

If you elect to read the Contributor Documents later, you will learn
about how the pylint source-code checker is used in the OSPC-ACA
project.  But, at this point, there is no reason to learn more.

<b>Using Python to Execute Source Code</b>

To check that everything is working as expected, change directory
to <em>OSPC-ACA-<version></em> and at the operating-system command
prompt in that directory, enter the following command:

<tt>OSPC-ACA-<version>$ python tests.py</tt>

If Python is correctly installed and the project files have been
downloaded successfully, the tests.py script should execute in less
than a minute without writing any output to the screen.  If you
have a problem, please use [/reportlist|this link] to create a new
ticket that describes your problem.

If you pass the tests, begin exploring the <tt>ptc.py</tt> script by
entering the following commands for information:

<tt>OSPC-ACA-<version>$ python ptc.py --help</tt><br>
<tt>OSPC-ACA-<version>$ python ptc.py --sample_format</tt><br>
<tt>OSPC-ACA-<version>$ python ptc.py --output_format</tt>

and by entering the following command to see the script in action:

<tt>OSPC-ACA-<version>$ python ptc.py</tt>

Next read about how to create your own [./sample.wiki|sample files].

Changes to www/policy.wiki.

103
104
105
106
107
108
109

110
111
112

113
114
115
116
117
118
119
120
...
158
159
160
161
162
163
164
165
166
167
168
169
170
contents of the <tt>sample_18_example</tt> file are as follows:

<tt>1 2018 CO 3 1 24000 0 1 60</tt>

The <tt>ptc.py</tt> script output for this sample file and the two
policy files described above are as follows:


<tt>python ptc.py sample_18_example aca_current_law.json</tt><br>
<tt>1 4397.92 194 6.02 1444.80 1 5842.72</tt>


<tt>python ptc.py sample_18_example aca_higher_prem.json</tt><br>
<tt>1 4598.54 194 6.02 1444.80 1 6043.34</tt>

The output shows that this individual has income equal to 194 percent
of the federal poverty level, which implies that under current-law ACA
policy this individual is expected to pay slightly more than six
percent of income on health insurance, which comes to almost 1445
dollars.  These results are the same in the two runs because the
................................................................................
manage your changes to the source code.  When you have finished making
and testing the structural changes, you will have the option to
contribute your changes, in the spirit of the open-source community,
to the OSPC-ACA project.  To learn how to clone the version-control
repository, to begin making structural changes in the OSPC-ACA PTC
calculator, and to contribute your changes to the broader community,
finish reading the User Documents (see below) and then read the
Developer Documents listed on the Documentation page.

<b>Next Step in Reading User Documents</b>

The historical state data that is automatically read by the
<tt>ptc.py</tt> script is described [./statedata.wiki|here].







>
|


>
|







 







|





103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
...
160
161
162
163
164
165
166
167
168
169
170
171
172
contents of the <tt>sample_18_example</tt> file are as follows:

<tt>1 2018 CO 3 1 24000 0 1 60</tt>

The <tt>ptc.py</tt> script output for this sample file and the two
policy files described above are as follows:

<tt>OSPC-ACA-<version>$ python ptc.py sample_18_example
                               aca_current_law.json</tt><br>
<tt>1 4397.92 194 6.02 1444.80 1 5842.72</tt>

<tt>OSPC-ACA-<version>$ python ptc.py sample_18_example
                               aca_higher_prem.json</tt><br>
<tt>1 4598.54 194 6.02 1444.80 1 6043.34</tt>

The output shows that this individual has income equal to 194 percent
of the federal poverty level, which implies that under current-law ACA
policy this individual is expected to pay slightly more than six
percent of income on health insurance, which comes to almost 1445
dollars.  These results are the same in the two runs because the
................................................................................
manage your changes to the source code.  When you have finished making
and testing the structural changes, you will have the option to
contribute your changes, in the spirit of the open-source community,
to the OSPC-ACA project.  To learn how to clone the version-control
repository, to begin making structural changes in the OSPC-ACA PTC
calculator, and to contribute your changes to the broader community,
finish reading the User Documents (see below) and then read the
Contributor Documents listed on the Documentation page.

<b>Next Step in Reading User Documents</b>

The historical state data that is automatically read by the
<tt>ptc.py</tt> script is described [./statedata.wiki|here].

Changes to www/sample.wiki.

4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
as described [./download.wiki|here].

The <tt>ptc.py</tt> script reads a sample file that contains
ACA-relevant information for one or more federal income tax filing
units.  Enter the following command to see details of the sample file
format:

<tt>python ptc.py --sample_format</tt>

The <tt>ptc.py</tt> script writes output for each income tax filing
unit in the sample file, where the output contains the tax filing
unit's refundable ACA premium tax credit (PTC) as computed on IRS Form
8962 as well as several intermediate amounts.  Enter the following
command to see details of the output format:

<tt>python ptc.py --output_format</tt>

It appears as if there is no publicly-available national survey data
set that contains all the information needed for the <tt>ptc.py</tt>
sample file, which is the minimal information required to compute
accurately a filing unit's PTC.  As a result of this situation, the
OSPC-ACA project has not yet produced a <tt>ptc.py</tt> sample file
that is representative of the US population.
................................................................................
fifty states and DC that is provided at
[http://www.cms.gov/cciio/programs-and-initiatives/health-insurance-market-reforms/state-gra.html|this
CMS website].

After you create a sample file (assume it is called <tt>my_sample</tt>),
compute the PTC amounts by entering the following command:

<tt>python ptc.py my_sample</tt>

or by entering the equivalent command:

<tt>python ptc.py my_sample aca_current_law.json</tt>

Both commands will produce the same results because the default value
of the policy_filename positional argument is <tt>aca_current_law.json</tt>.

To save the output produced by the <tt>ptc.py</tt> script to a file,
redirect the output from stdout (the screen) to a file as in the
following example:

<tt>python ptc.py my_sample > my_sample.out</tt>

To use projection assumptions and/or policy parameters that differ from
those in <tt>aca_current_law.json</tt>, create a new policy input file as
described [./policy.wiki|here].







|







|







 







|












|




4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
as described [./download.wiki|here].

The <tt>ptc.py</tt> script reads a sample file that contains
ACA-relevant information for one or more federal income tax filing
units.  Enter the following command to see details of the sample file
format:

<tt>OSPC-ACA-<version>$ python ptc.py --sample_format</tt>

The <tt>ptc.py</tt> script writes output for each income tax filing
unit in the sample file, where the output contains the tax filing
unit's refundable ACA premium tax credit (PTC) as computed on IRS Form
8962 as well as several intermediate amounts.  Enter the following
command to see details of the output format:

<tt>OSPC-ACA-<version>$ python ptc.py --output_format</tt>

It appears as if there is no publicly-available national survey data
set that contains all the information needed for the <tt>ptc.py</tt>
sample file, which is the minimal information required to compute
accurately a filing unit's PTC.  As a result of this situation, the
OSPC-ACA project has not yet produced a <tt>ptc.py</tt> sample file
that is representative of the US population.
................................................................................
fifty states and DC that is provided at
[http://www.cms.gov/cciio/programs-and-initiatives/health-insurance-market-reforms/state-gra.html|this
CMS website].

After you create a sample file (assume it is called <tt>my_sample</tt>),
compute the PTC amounts by entering the following command:

<tt>OSPC-ACA-<version>$ python ptc.py my_sample</tt>

or by entering the equivalent command:

<tt>python ptc.py my_sample aca_current_law.json</tt>

Both commands will produce the same results because the default value
of the policy_filename positional argument is <tt>aca_current_law.json</tt>.

To save the output produced by the <tt>ptc.py</tt> script to a file,
redirect the output from stdout (the screen) to a file as in the
following example:

<tt>OSPC-ACA-<version>$ python ptc.py my_sample > my_sample.out</tt>

To use projection assumptions and/or policy parameters that differ from
those in <tt>aca_current_law.json</tt>, create a new policy input file as
described [./policy.wiki|here].

Changes to www/validation.wiki.

73
74
75
76
77
78
79







Kaiser calculator apparently does not use integer values of magi_pct,
and therefore, a few large differences occur for tax filing units with
magi_pct values close to where the function experiences a
discontinuity (for example, at 100 and 400 magi_pct).  But overall,
there is extensive and close agreement between the Kaiser calculator
results and the results produced by the <tt>ptc.py</tt> script for
2015.














>
>
>
>
>
>
>
73
74
75
76
77
78
79
80
81
82
83
84
85
86
Kaiser calculator apparently does not use integer values of magi_pct,
and therefore, a few large differences occur for tax filing units with
magi_pct values close to where the function experiences a
discontinuity (for example, at 100 and 400 magi_pct).  But overall,
there is extensive and close agreement between the Kaiser calculator
results and the results produced by the <tt>ptc.py</tt> script for
2015.

This is the last User Document.  You can elect to stop reading the
documentation here, or continue if one of the two conditions is true.
If you want to learn about using a version-control system to increase
your productivity in using the OSPC-ACA source code, or if you want to
learn about how to contribute your enhancements to the OSPC-ACA source
code, begin reading the [./cloningrepo.wiki|Contributor Documents].