• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..06-Jun-2021-

READMEH A D12-Jan-20213.8 KiB7763

boot.rH A D11-Jan-20211.7 KiB7056

brute.rH A D26-Apr-20111.1 KiB5337

combos.rH A D02-Sep-20161.4 KiB8370

crqfnb.rH A D26-Apr-20111.5 KiB5428

grexp.rH A D30-Nov-2020143 139

kuantiles.rH A D09-Nov-2020334 1510

penalty.rH A D26-Apr-20113.8 KiB14098

pfnb.rH A D18-Dec-20203.6 KiB145110

powell.rH A D11-Jan-20212.9 KiB150121

pwxy.rH A D12-Jan-20213.2 KiB12693

qfnb.rH A D18-Nov-20201 KiB4423

qselect.rH A D10-Jan-20211.1 KiB5851

rls.rH A D11-Jan-2021621 2817

rqbr.rH A D06-Aug-201913.9 KiB569475

rqfn.rH A D26-Apr-20116.5 KiB209135

rqfnb.rH A D18-Jun-20195.1 KiB171133

rqfnc.rH A D10-Jan-20157 KiB219175

rqs.rH A D22-Jul-2011306 108

sakj.rH A D19-Jan-20213.5 KiB12595

README

1This directory contains ratfor source for the several routines of the
2rq library.  These are not strictly necessary, but they may prove useful
3to anyone wanting to look at the source in detail, since the fortran
4translation of them by the ratfor compiler is far from readable.
5
6Note added September 17, 2004
7
8Apparently g77 v3.4 doesn't like double precision data statements so
9these have been changed to parameter() declarations.  This turned out
10to be a bug in g77, but the deed is done so I've left the parameter
11statements in place of the original data statements.  However, this
12entailed the dangerous step of installing the SEP ratfor77 translator.
13(See http://sepwww.stanford.edu/software/ratfor.html for details.)
14
15Past experience, and now a bug file in the SEP distro, suggests
16that the ratfor switch statement is unlikely to be correctly handled.
17Fortunately, none of the included routines in the directory use switch
18but caution is undoubtedly indicated.  The fortran produced for rqbr.r
19is somewhat different than that produced by my older sun version, and
20generates two warnings from g77, but these appear to be harmless.
21
22Note added March 16, 2005
23
24g77 has been issuing warnings for the code generated from the
25SEP distro of ratfor version of rqbr.r for a while now, but
26yesterday Jan deLeeuw reported that it now generates an error
27in his gfortran 4.0 on osx.  After some comparisons with old
28version of the ratfor translation, in particular the rq.f in
29rq/statlib.95 on ysidro, I determined that what the compiler
30didn't like was the way that if-endifs were generated by
31the SEP translation.  So.... I hand edited these last few
32if-endifs in the .f file, and move that back into the src
33directory. This is TOTALLY unsatisfactory, since it means
34that this needs to be done yet again if any changes are
35made to the ratfor code, but seems to be the cost of  using
36the SEP translator.  A more clever guy with more time could
37probably find a way to change the ratfor, but given other
38constraints that ain't going to happen anytime soon.  Note
39that I've for future reference put a version of the old rq.f
40file generated by my old BTL ratfor translator into this
41directory. as well as the new rqbr.f.
42
43Note added Oct 22, 2007
44
45As part of the development of the crqfnb function I downloaded
46the SEP version of ratfor77, which seems to work ok on this
47function.  It is installed in my $HOME/bin directory and the
48build is in the Rinstall directory.  Note that now on yzzy
49ratfor is called ratfor77.
50
51Note added May 14, 2016
52
53Contrary to the last note, it appears that my $HOME/bin/ratfor
54command works and $HOME/bin/ratfor77 does not.
55
56Note added Jan 22, 2020
57
58Contrary to the last note there is no $HOME/bin/ratfor* but I've installed
59ratfor90 in /usr/local/bin and this might produce something workable.  Not
60yet really tested seriously, but those ugly line numbers are gone, at least.
61
62Note added November 8 2020
63
64I've installed a new ratfor executable in my mac mini bin directory.  It
65is generated from Brian Gaeke's C distribution ratfor-1.05.  And seems to work
66well; i.e. produces .f files that compile with gfortran -c with only a couple
67of warnings about legacy syntax.  The good news is that these warnings are
68emitted only for the rqbr.f code produced from rqbr.r, for which my handedited
69rqbr.f version still passes R CMD check.  This was reported to Brian and he
70suggested flags that could be used to quell the emissions, but this didn't
71seem a.) very practical, or b.) very necessary.  I've put links to Brian G's
72code for ratfor and to Brian K's BTL memo describing ratfor on my
73reproducibility webpage.  So for the foreseeable, we are ok on the ratfor
74front, including for the new subroutines pfnb.r and qfnb.r.  To reiterate, all
75the ratfor in this directory, with the exception of rqbr.r is used to generate
76the fortran in the src directory above.
77