Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the R Core Team.

Next: Creating R packages , Previous: Writing R Extensions , Up: Writing R Extensions [ Contents ][ Index ]. The contributions to early versions of this manual by Saikat DebRoy who wrote the first draft of a guide to using. Call and. Next: Writing R documentation files , Previous: Acknowledgements , Up: Writing R Extensions [ Contents ][ Index ].

Packages provide a mechanism for loading optional code, data and documentation as needed. The R distribution itself includes about 30 packages. In the following, we assume that you know the library command, including its lib. loc argument, and we also assume basic knowledge of the R CMD INSTALL utility. Once a source package is created, it must be installed by the command R CMD INSTALL.

See Add-on-packages in R Installation and Administration. Other types of extensions are supported but rare : See Package types. Some notes on terminology complete this introduction. These will help with the reading of this manual, and also in describing concepts accurately when asking for help. A package is a directory of files which extend R, a source package the master files of a package , or a tarball containing the files of a source package, or an installed package, the result of running R CMD INSTALL on a source package.

On some platforms notably macOS and Windows there are also binary packages , a zip file or tarball containing the files of an installed package which can be unpacked rather than installing from sources. A package is not 1 a library.

The latter is used in two senses in R documentation. The concept of lazy loading of code or data is mentioned at several points. This is part of the installation, always selected for R code but optional for data. When used the R objects of the package are created at installation time and stored in a database in the R directory of the installed package, being loaded into the session at first use.

This makes the R session start up faster and use less virtual memory. For technical details, see Lazy loading in R Internals. CRAN is a network of WWW sites holding the R distributions and contributed code, especially R packages.

shtml submitting. Next: Configure and cleanup , Previous: Creating R packages , Up: Creating R packages [ Contents ][ Index ]. The package subdirectory may also contain files INDEX , configure , cleanup , LICENSE , LICENCE and NEWS.

md 2 , or ChangeLog will be ignored by R, but may be useful to end users. The utility R CMD build may add files in a build directory but this should not be used for other purposes.

The NAMESPACE file is described in the section on Package namespaces. The optional files configure and cleanup are Bourne shell scripts which are, respectively, executed before and if option --clean was given after installation on Unix-alikes, see Configure and cleanup.

The analogues on Windows are configure. win and cleanup. Since R 4. ucrt and cleanup. ucrt are supported and take precedence over configure.

They can hence be used to provide content specific for UCRT or Rtools42, if needed, but the support for. ucrt files may be removed in the future when building packages from source on the older versions of R will no longer be needed, and hence the files may be renamed back to. html Documentation. The package subdirectory should be given the same name as the package. Because some file systems e. For example, if you have a package named foo , do not also create a package named Foo.

Also, file names in the same directory must not differ only by case see the previous paragraph. For maximal portability filenames should only contain only ASCII characters not excluded already that is A-Za-z In addition, packages are normally distributed as tarballs, and these have a limit on path lengths: for maximal portability bytes. A source package if possible should not contain binary executable files: they are not portable, and a security risk if they are of the appropriate architecture.

R CMD check will warn about them 4 unless they are listed one filepath per line in a file BinaryFiles at the top level of the package. Note that CRAN will not accept submissions containing binary files even if they are listed. The R function package. skeleton can help to create the structure for a new package: see its help page for details.

Next: Licensing , Previous: Package structure , Up: Package structure [ Contents ][ Index ]. Fields start with an ASCII name immediately followed by a colon: the value starts after the colon and a space. Continuation lines for example, for descriptions longer than one line start with a space or tab.

Field names are case-sensitive: all those used by R are capitalized. This should contain only ASCII letters, numbers and dot, have at least two characters and start with a letter and not end in a dot.

It is not a decimal number, so for example 0. Some package listings may truncate the title to 65 characters. It should use title case that is, use capitals for the principal words: tools::toTitleCase can help you with this , not use any markup, not have any continuation lines, and not end in a period unless part of …. Do not repeat the package name: it is often used prefixed by the name.

Refer to other packages and external software in single quotes, and to book titles and similar in double quotes. One can use several complete sentences, but only one paragraph. It should be intelligible to all the intended readership e. for a CRAN package to all CRAN users. This field should also be used for explaining the package name if necessary.

URLs should be enclosed in angle brackets, e. Note that all significant contributors must be included: if you wrote an R wrapper for the work of others included in the src directory, you are not the sole and maybe not even the main author. It should not end in a period or comma. This field is what is reported by the maintainer function and used by bug. For a CRAN package it should be a person , not a mailing list and not a corporate entity: do ensure that it is valid and will remain valid for the lifetime of the package.

Note that the display name the part before the address in angle brackets should be enclosed in double quotes if it contains non-alphanumeric characters such as comma or period.

The current standard, RFC , allows periods but RFC did not. person for more information. Note that no role is assumed by default. Auto-generated package citation information takes advantage of this specification. These URL s are converted to active hyperlinks in CRAN package listings. See Specifying URLs. This URL will be used by bug.

report instead of sending an email to the maintainer. Base and recommended packages i. These priorities must not be used by other packages. If present, the collate specification must list all R code files in the package taking possible OS-specific subdirectories into account, see Package subdirectories as a whitespace separated list of file paths relative to the R subdirectory. Paths containing white space or quotes need to be quoted.

This can be overridden by installing with flag --no-byte-compile. This can be overridden by the flags --use-LTO and --no-use-LTO. This field was introduced in R 3. This should only be used exceptionally, for example if the PDFs include large figures which are not part of the package sources and hence only in packages which do not have an Open Source license.

The utils package is always implicitly appended. See Non-Sweave vignettes for details. Rd files. The examples are assumed to be in this encoding when running R CMD check , and it is used for the encoding of the CITATION file.

Only encoding names latin1 , latin2 and UTF-8 are known to be portable. Do not specify an encoding unless one is actually needed: doing so makes the package less portable. If a package has a specified encoding, you should run R CMD build etc in a locale using that encoding. This is used by install. html ; the former refers to the version.

The subject classifications should be comma-separated lists of the respective classification codes, e. Macro definitions in individual. Rd files in the man directory are loaded last, and are local to later parts of that file. In case of duplicates, the last loaded definition will be used. Packages using Rd macros should depend on R 3.

There is no restriction on the use of other fields not mentioned here but using other capitalizations of these field names would cause confusion. Some repositories including CRAN and R-forge add their own fields. Licensing for a package which might be distributed is an important but potentially complex subject.

It is very important that you include license information! Otherwise, it may not even be legally correct for others to distribute copies of the package, let alone use it. Others need to ensure that there are no restrictions stopping them using a package, e. forbidding commercial or military use. It is a central tenet of FOSS software that there are no restrictions on users nor usage. Alternatives are indicated via vertical bars. Individual specifications must be one of.

Abbreviations GPL and LGPL are ambiguous and usually 10 taken to mean any version of the license: but it is better not to use them. If a package license restricts a base license where permitted, e. Note that several commonly used licenses do not permit restrictions: this includes GPL-2 and hence any specification which includes it.

These are used by, e. packages filters. Whereas you should feel free to include a license file in your source distribution, please do not arrange to install yet another copy of the GNU COPYING or COPYING. Since files named LICENSE or LICENCE will be installed, do not use these names for standard license files.

To include comments about the licensing rather than the body of a license, use a file named something like LICENSE. Next: The INDEX file , Previous: Licensing , Up: Package structure [ Contents ][ Index ]. Those packages will be attached before the current package when library or require is called. Each package name may be optionally followed by a comment in parentheses specifying a version requirement.

The comment should contain a comparison operator, whitespace and a valid version number, e. As here, trailing zeroes can be dropped and it is recommended that they are. You can also require a certain SVN revision for R-devel or R-patched, e. It makes no sense to declare a dependence on R without a version specification, nor on the package base : this is an R package and package base is always available.

It is inadvisable to use a dependence on R with patchlevel the third digit other than zero. Doing so with packages which others depend on will cause the other packages to become unusable under earlier versions in the series, and e. versions 4. The R INSTALL facilities check if the version of R used is recent enough for the package being installed, and the list of packages which is specified will be attached after checking version requirements before the current package.

Version requirements can be specified and are checked when the namespace is loaded. This includes packages used only in examples, tests or vignettes see Writing package vignettes , and packages loaded in the body of functions. Version requirements can be specified but should be checked by the code which uses the package. Version requirements can be specified, but are currently not used.

Such packages cannot be required to check the package: any tests which use them must be conditional on the presence of the package. If your tests use e.

It is important that the information in these fields is complete and accurate: it is for example used to compute which packages depend on an updated package and which packages can safely be installed in parallel. This scheme was developed before all packages had namespaces R 2. This is checked by R CMD check. R code in the package should call library or require only exceptionally.

For example. This includes CRAN package BH and almost all users of RcppArmadillo and RcppEigen. It is currently used by R CMD check to check that the packages can be found, at least as source packages which can be installed on any platform. Previous: Package Dependencies , Up: Package Dependencies [ Contents ][ Index ].

However, using require for conditioning in package code is not good practice as it alters the search path for the rest of the session and relies on functions in that package not being masked by other require or library calls.

It is better practice to use code like. Note the use of rgl:: as that object would not necessarily be visible and if it is, it need not be the one from that namespace: plot3d occurs in several other packages.

If the intention is to give an error if the suggested package is not available, simply use e. If the conditional code produces print output, function withAutoprint can be useful. Note that the recommendation to use suggested packages conditionally in tests does also apply to packages used to manage test suites: a notorious example was testthat which in version 1.

It is recommended that a package is checked with each of these set, as well as with neither. WARNING: Be extremely careful if you do things which would be run at installation time depending on whether suggested packages are available or not—this includes top-level code in R code files,.

onLoad functions and the definitions of S4 classes and methods. The problem is that once a namespace of a suggested package is loaded, references to it may be captured in the installed package most commonly in S4 methods , but the suggested package may not be available when the installed package is used which especially for binary packages might be on a different machine.

Even worse, the problems might not be confined to your package, for the namespaces of your suggested packages will also be loaded whenever any package which imports yours is installed and so may be captured there. Next: Package subdirectories , Previous: Package Dependencies , Up: Package structure [ Contents ][ Index ]. The optional file INDEX contains a line for each sufficiently interesting object in the package, giving its name and a description functions such as print methods not usually called explicitly might not be included.

Normally this file is missing and the corresponding information is automatically generated from the documentation sources using tools::Rdindex when installing from source. Next: Data in packages , Previous: The INDEX file , Up: Package structure [ Contents ][ Index ]. The R subdirectory contains R code files, only. The code files to be installed must start with an ASCII lower or upper case letter or digit and have one of the extensions We recommend using.

R , as this extension seems to be not used by any other software. It should be possible to read in the files using source , so R objects must be created by assignments.

Note that there need be no connection between the name of the file and the R objects created by it. Ideally, the R code files should only directly assign R objects and definitely should not call functions with side effects such as require and options.

Extreme care is needed if top-level computations are made to depend on availability or not of other packages. In particular this applies to setMethods and setClass calls. Nor should they depend on the availability of external resources such as downloads. Two exceptions are allowed: if the R subdirectory contains a file sysdata. this will be lazy-loaded into the namespace environment — this is intended for system datasets that are not intended to be user-accessible via data.

Only ASCII characters and the control characters tab, formfeed, LF and CR should be used in code files. Other characters are accepted in comments 14 , but then the comments may not be readable in e.

a UTF-8 locale. Non- ASCII characters in object names will normally 15 fail when the package is installed. However, non- ASCII character strings may not be usable in some locales and may display incorrectly in others. Various R functions in a package can be used to initialize and clean up. See Load hooks. The man subdirectory should contain only documentation files for the objects in the package in R documentation Rd format.

The documentation filenames must start with an ASCII lower or upper case letter or digit and have the extension. Rd the default or. See Writing R documentation files , for more information. Rd which documents all such objects, and clearly states that these are not meant to be called by the user. See e. the sources for package grid in the R distribution.

Note that packages which use internal objects extensively should not export those objects from their namespace, when they do not need to be documented see Package namespaces. Having a man directory containing no documentation files may give an installation error. The man subdirectory may contain a subdirectory named macros ; this will contain source for user-defined Rd macros.

See User-defined macros. These use the Rd format, but may not contain anything but macro definitions, comments and whitespace. The R and man subdirectories may contain OS-specific subdirectories named unix or windows.

The sources and headers for the compiled code are in src , plus optionally a file Makevars or Makefile. When a package is installed using R CMD INSTALL , make is used to control compilation and linking into a shared object for loading into R. cc or. cpp ,. f90 or. f95 ,. m , and. mm , respectively. Use of extension. Files in the src directory should not be hidden start with a dot , and hidden files will under some versions of R be ignored.

It is not portable and may not be possible at all to mix all these languages in a single package. If such a file is to be distributed, considerable care is needed to make it general enough to work on all R platforms. win must be used. ucrt will be ignored by earlier versions of R, and hence can be used to provide content specific for UCRT or Rtools42, but the support for.

Some make programs require makefiles to have a complete final line, including a newline. A few packages use the src directory for purposes other than making a shared object e.

to create executables. ucrt unless intended for only Unix-alikes or only Windows. R file:. The data subdirectory is for data files: See Data in packages. The demo subdirectory is for R scripts for running via demo that demonstrate some of the functionality of the package.

Demos may be interactive and are not checked automatically, so if testing is desired use code in the tests directory to achieve this. The script files must start with a lower or upper case letter and have one of the extensions.

If present, the demo subdirectory should also have a 00Index file with one line for each demo, giving its name and a description separated by a tab or at least three spaces. This index file is not generated automatically. Note that a demo does not have a specified encoding and so should be an ASCII file see Encoding issues. Function demo will use the package encoding if there is one, but this is mainly useful for non- ASCII comments.

The contents of the inst subdirectory will be copied recursively to the installation directory. Subdirectories of inst should not interfere with those used by R currently, R , data , demo , exec , libs , man , help , html and Meta , and earlier versions used latex , R-ex.

The copying of the inst happens after src is built so its Makefile can create files to be installed. To exclude files from being installed, one can specify a list of exclude patterns in file. Rinstignore in the top-level source directory. These patterns should be Perl-like regular expressions see the help for regexp in R for the precise details , one per line, to be matched case-insensitively against the file and directory paths, e.

packages on the tarball. So any information files you wish an end user to see should be included in inst. Note that if the named exceptions also occur in inst , the version in inst will be that seen in the installed package. Things you might like to add to inst are a CITATION file for use by the citation function, and a NEWS. Rd file for use by the news function. See its help page for the specific format restrictions of the NEWS. Rd file. Subdirectory tests is for additional package-specific test code, similar to the specific tests that come with the R distribution.

Test code can either be provided directly in a. Rin file containing code which in turn creates the corresponding. R file e. The results of running a. R file are written to a. Rout file. If there is a corresponding save file, these two are compared, with differences being reported but not causing an error.

Note that the package-specific tests are run in a vanilla R session without setting the random-number seed, so tests which use random numbers will need to set the seed to obtain reproducible results and it can be helpful to do so in all cases, to avoid occasional failures when tests are run. If directory tests has a subdirectory Examples containing a file pkg -Ex. save , this is compared to the output file for running the examples when the latter are checked.

Reference output should be produced without having the --timings option set and note that --as-cran sets it. Things which trip up maintainers include displayed version numbers from loading other packages, printing numerical results to an unreproducibly high precision and printing timings. Another trap is small values which are in fact rounding error from zero: consider using zapsmall.

Subdirectory exec could contain additional executable scripts the package needs, typically scripts for interpreters such as the shell, Perl, or Tcl. Note too that this is not suitable for executable programs since some platforms including Windows support multiple architectures using the same installed package directory.

Subdirectory po is used for files related to localization : see Internationalization. Subdirectory tools is the preferred place for auxiliary files needed during configuration, and also for sources need to re-create scripts e.

M4 files for autoconf : some prefer to put those in a subdirectory m4 of tools. Next: Non-R scripts in packages , Previous: Package subdirectories , Up: Package structure [ Contents ][ Index ]. The data subdirectory is for data files, either to be made available via lazy-loading or for loading using data.

Data files can have one of three types as indicated by their extension: plain R code. r , tables. tab ,. txt , or. csv , see? data for the file formats, and note that. csv is not the standard 22 CSV format , or save images. RData or. The files should not be hidden have names starting with a dot.

Images extensions. RData 23 or. rda can contain references to the namespaces of packages that were used to create them. Preferably there should be no such references in data files, and in any case they should only be to packages listed in the Depends and Imports fields, as otherwise it may be impossible to install the package.

To check for such references, load all the images into a vanilla R session, run str on all the datasets, and look at the output of loadedNamespaces. Particular care is needed where a dataset or one of its components is of an S4 class, especially if the class is defined in a different package. First, the package containing the class definition has to be available to do useful things with the dataset, so that package must be listed in Imports or Depends even if this gives a check warning about unused imports.

Second, the definition of an S4 class can change, and often is unnoticed when in a package with a different author. So it may be wiser to use the. R scripts to produce your data, loading your namespace, you can speed up installation by providing a file datalist in the data subdirectory. csv files can be compressed by gzip , bzip2 or xz , optionally with additional extension.

bz2 or. If your package is to be distributed, do consider the resource implications of large datasets for your users: they can make packages very slow to download and use up unwelcome amounts of storage space, as well as taking many seconds to load. It is normally best to distribute large datasets as. Using bzip2 or xz compression will usually reduce the size of both the package tarball and the installed package, in some cases by a factor of two or more.

Package tools has a couple of functions to help with data images: checkRdaFiles reports on the way the image was saved, and resaveRdaFiles will re-save with a different type of compression, including choosing the best type for that particular image. Useful values are bzip2 , xz and the default, gzip : value none is also accepted.

rdb file. A function to do that quoting sizes in KB is. If you see that, run CheckLazyDataCompression and set the field — to gzip in the unlikely event 24 that is the best choice. The analogue for sysdata. Lazy-loading is not supported for very large datasets those which when serialized exceed 2GB, the limit for the format on bit platforms.

Next: Specifying URLs , Previous: Data in packages , Up: Package structure [ Contents ][ Index ]. Subdirectory exec could be used for scripts for interpreters such as the shell, BUGS, JavaScript, Matlab, Perl, php amap , Python or Tcl Simile , or even R. Java code is a special case: except for very small programs,. java files should be byte-compiled to a. class file and distributed as part of a. jar file: the conventional location for the. It is desirable and required under an Open Source license to make the Java source files available: this is best done in a top-level java directory in the package—the source files should not be installed.

This is fairly easy to do: first find the Tcl search path:. If no location on that search path is writeable, you will need to add one each time BWidget is to be used with tcltk::addTclPath. gz , but needed patching for current Tk 8. Previous: Non-R scripts in packages , Up: Package structure [ Contents ][ Index ]. URLs in many places in the package documentation will be converted to clickable hyperlinks in at least some of their renderings. So care is needed that their forms are correct and portable.

Spaces in URLs are not portable and how they are handled does vary by HTTP server and by client. Next: Checking and building packages , Previous: Package structure , Up: Creating R packages [ Contents ][ Index ]. Note that most of this section is specific to Unix-alikes: see the comments later on about the Windows port of R. If your package needs some system-dependent configuration before installation you can include an executable Bourne 26 shell script configure in your package which if present is executed by R CMD INSTALL before any other action is performed.

This can be a script created by the Autoconf mechanism, but may also be a script written by yourself. Use this to detect if any nonstandard libraries are present such that corresponding code in the package can be disabled at install time rather than giving error messages when the package is compiled or used.

To summarize, the full power of Autoconf is available for your extension package including variable substitution, searching for libraries, etc. Under a Unix-alike only, an executable Bourne shell script cleanup is executed as the last thing by R CMD INSTALL if option --clean was given, and by R CMD build when preparing the package for building from its source. As an example consider we want to use functionality provided by a C or Fortran library foo. For example, if a function named bar is to be made available by linking against library foo i.

From this file configure creates the actual R source file foo. R looking like. if library foo was not found with the desired functionality. In this case, the above R code effectively disables the function.

One could also use different file fragments for available and missing functionality, respectively. You will very likely need to ensure that the same C compiler and compiler flags are used in the configure tests as when compiling R or your package. Under a Unix-alike, you can achieve this by including the following fragment early in configure. If your code does load checks for example, to check for an entry point in a library or to run code then you will also need.

You can use R CMD config to get the value of the basic configuration variables, and also the header and library flags necessary for linking a front-end executable program against R, see R CMD config --help for details. Note that FLIBS as determined by R must be used to ensure that Fortran code works on all R platforms.

Otherwise R CMD build may ship the files that are created. For example, package RODBC has. As this example shows, configure often creates working files such as config. If your configure script needs auxiliary files, it is recommended that you ship them in a tools directory as R itself does.

You should bear in mind that the configure script will not be used on Windows systems. If your package is to be made publicly available, please give enough information for a user on a non-Unix-alike platform to configure it manually, or provide a configure. win script or configure. ucrt to be used on that platform. Optionally, there can be a cleanup. win script or cleanup. Both should be shell scripts to be executed by ash , which is a minimal version of Bourne-style sh.

When configure. win or configure. In some rare circumstances, the configuration and cleanup scripts need to know the location into which the package is being installed. Usually, the object that is dynamically loaded by R is linked against the second, dependent, object. On some systems, we can add the location of this dependent object to the object that is dynamically loaded by R. Another example is when a package installs support files that are required at run time, and their location is substituted into an R data structure at installation time.

Majorities across all demographic groups and partisan groups, as well as across regions, are pessimistic about the direction of the United States. A wide partisan divide exists: most Democrats and independents say their financial situation is about the same as a year ago, while solid majorities of Republicans say they are worse off.

Regionally, about half in the San Francisco Bay Area and Los Angeles say they are about the same, while half in the Central Valley say they are worse off; residents elsewhere are divided between being worse off and the same.

The shares saying they are worse off decline as educational attainment increases. Strong majorities across partisan groups feel negatively, but Republicans and independents are much more likely than Democrats to say the economy is in poor shape.

Today, majorities across partisan, demographic, and regional groups say they are following news about the gubernatorial election either very or fairly closely. In the upcoming November 8 election, there will be seven state propositions for voters. Due to time constraints, our survey only asked about three ballot measures: Propositions 26, 27, and For each, we read the proposition number, ballot, and ballot label.

Two of the state ballot measures were also included in the September survey Propositions 27 and 30 , while Proposition 26 was not. This measure would allow in-person sports betting at racetracks and tribal casinos, requiring that racetracks and casinos offering sports betting make certain payments to the state to support state regulatory costs. It also allows roulette and dice games at tribal casinos and adds a new way to enforce certain state gambling laws.

Fewer than half of likely voters say the outcome of each of these state propositions is very important to them. Today, 21 percent of likely voters say the outcome of Prop 26 is very important, 31 percent say the outcome of Prop 27 is very important, and 42 percent say the outcome of Prop 30 is very important.

Today, when it comes to the importance of the outcome of Prop 26, one in four or fewer across partisan groups say it is very important to them. About one in three across partisan groups say the outcome of Prop 27 is very important to them. Fewer than half across partisan groups say the outcome of Prop 30 is very important to them. When asked how they would vote if the election for the US House of Representatives were held today, 56 percent of likely voters say they would vote for or lean toward the Democratic candidate, while 39 percent would vote for or lean toward the Republican candidate.

Democratic candidates are preferred by a point margin in Democratic-held districts, while Republican candidates are preferred by a point margin in Republican-held districts. Abortion is another prominent issue in this election. When asked about the importance of abortion rights, 61 percent of likely voters say the issue is very important in determining their vote for Congress and another 20 percent say it is somewhat important; just 17 percent say it is not too or not at all important. With the controlling party in Congress hanging in the balance, 51 percent of likely voters say they are extremely or very enthusiastic about voting for Congress this year; another 29 percent are somewhat enthusiastic while 19 percent are either not too or not at all enthusiastic.

Today, Democrats and Republicans have about equal levels of enthusiasm, while independents are much less likely to be extremely or very enthusiastic. As Californians prepare to vote in the upcoming midterm election, fewer than half of adults and likely voters are satisfied with the way democracy is working in the United States—and few are very satisfied.

Satisfaction was higher in our February survey when 53 percent of adults and 48 percent of likely voters were satisfied with democracy in America. Today, half of Democrats and about four in ten independents are satisfied, compared to about one in five Republicans.

Notably, four in ten Republicans are not at all satisfied. In addition to the lack of satisfaction with the way democracy is working, Californians are divided about whether Americans of different political positions can still come together and work out their differences. Forty-nine percent are optimistic, while 46 percent are pessimistic. Today, in a rare moment of bipartisan agreement, about four in ten Democrats, Republicans, and independents are optimistic that Americans of different political views will be able to come together.

Notably, in , half or more across parties, regions, and demographic groups were optimistic. Today, about eight in ten Democrats—compared to about half of independents and about one in ten Republicans—approve of Governor Newsom. Across demographic groups, about half or more approve of how Governor Newsom is handling his job. Approval of Congress among adults has been below 40 percent for all of after seeing a brief run above 40 percent for all of Democrats are far more likely than Republicans to approve of Congress.

Fewer than half across regions and demographic groups approve of Congress. Approval in March was at 44 percent for adults and 39 percent for likely voters. Across demographic groups, about half or more approve among women, younger adults, African Americans, Asian Americans, and Latinos.

Views are similar across education and income groups, with just fewer than half approving. Approval in March was at 41 percent for adults and 36 percent for likely voters. Across regions, approval reaches a majority only in the San Francisco Bay Area.

Across demographic groups, approval reaches a majority only among African Americans. This map highlights the five geographic regions for which we present results; these regions account for approximately 90 percent of the state population. Residents of other geographic areas in gray are included in the results reported for all adults, registered voters, and likely voters, but sample sizes for these less-populous areas are not large enough to report separately.

The PPIC Statewide Survey is directed by Mark Baldassare, president and CEO and survey director at the Public Policy Institute of California.

Coauthors of this report include survey analyst Deja Thomas, who was the project manager for this survey; associate survey director and research fellow Dean Bonner; and survey analyst Rachel Lawler. The Californians and Their Government survey is supported with funding from the Arjay and Frances F.

Findings in this report are based on a survey of 1, California adult residents, including 1, interviewed on cell phones and interviewed on landline telephones. The sample included respondents reached by calling back respondents who had previously completed an interview in PPIC Statewide Surveys in the last six months. Interviews took an average of 19 minutes to complete.

Interviewing took place on weekend days and weekday nights from October 14—23, Cell phone interviews were conducted using a computer-generated random sample of cell phone numbers. Additionally, we utilized a registration-based sample RBS of cell phone numbers for adults who are registered to vote in California. All cell phone numbers with California area codes were eligible for selection. After a cell phone user was reached, the interviewer verified that this person was age 18 or older, a resident of California, and in a safe place to continue the survey e.

Cell phone respondents were offered a small reimbursement to help defray the cost of the call. Cell phone interviews were conducted with adults who have cell phone service only and with those who have both cell phone and landline service in the household.

Landline interviews were conducted using a computer-generated random sample of telephone numbers that ensured that both listed and unlisted numbers were called.

Additionally, we utilized a registration-based sample RBS of landline phone numbers for adults who are registered to vote in California. All landline telephone exchanges in California were eligible for selection. For both cell phones and landlines, telephone numbers were called as many as eight times. When no contact with an individual was made, calls to a number were limited to six. Also, to increase our ability to interview Asian American adults, we made up to three additional calls to phone numbers estimated by Survey Sampling International as likely to be associated with Asian American individuals.

Accent on Languages, Inc. The survey sample was closely comparable to the ACS figures. To estimate landline and cell phone service in California, Abt Associates used state-level estimates released by the National Center for Health Statistics—which used data from the National Health Interview Survey NHIS and the ACS.

The estimates for California were then compared against landline and cell phone service reported in this survey. We also used voter registration data from the California Secretary of State to compare the party registration of registered voters in our sample to party registration statewide.

The sampling error, taking design effects from weighting into consideration, is ±3. This means that 95 times out of , the results will be within 3. The sampling error for unweighted subgroups is larger: for the 1, registered voters, the sampling error is ±4.

For the sampling errors of additional subgroups, please see the table at the end of this section. Sampling error is only one type of error to which surveys are subject. Results may also be affected by factors such as question wording, question order, and survey timing. We present results for five geographic regions, accounting for approximately 90 percent of the state population.

Residents of other geographic areas are included in the results reported for all adults, registered voters, and likely voters, but sample sizes for these less-populous areas are not large enough to report separately. We also present results for congressional districts currently held by Democrats or Republicans, based on residential zip code and party of the local US House member. HTML5 的 canvas 元素使用 JavaScript 在网页上绘制图像。画布是一个矩形区域，您可以控制其每一像素。就是位图操作，可以理解为一个画图工具。可以任意对每个像素点进行任意操作之前讲解有一种断点类型叫做 事件监听断点，里面可以对canvas进行监听CanvasCreate canvas context 创建事件都选创建事件断点后，再刷页面断在这个地方：这里的代码用了流程平坦化打乱了最后的最后。.

将你的预期值和实际值进行比较，如果不一样，就是这种debugger 只能通过浏览器调用的堆栈区分出正确的逻辑。通过将editbreakpoint设置为false 可以禁用这个调试。通过hook方式，将运行的函数设为空就可以跳过debugger了。最好的方式就是不要被识别出来调试，可以通过下hook解决。非虚拟机的方式不会跳转 到一个vm的页面。在eval里面运行debugger. 我们的目的为了让js代码运行起来。可以不需要解密，将代码扣出来运行就可以。任何一个js类型的变量结果 加上一个字符串 ，只会变成字符串。所以这个调试起来很麻烦 只能单步调试 还是用解密工具解密。通过这种特性 可以组合成各种各样的加密方式。这个的原理就是将各种字符串加起来。2个值通过 运算会变成0或者1. js默认 支持Unicode的。所以支持所有的国家语种。有没有哪些国家的和O很像但不是O,和0很像但不是0,和p很像但不是p所以可以用这个相近的符号进行代码混淆。.

能修改输出js运行当中的一些变量的值能下断点批量监听一些变量值当渲染时，样式发生改变，会触发DOM断点它一般在 用户触发了某个事件 时，段下来。执行的比较考前，距离加密函数比较远。所以无法根据栈去快速定位。它的优点时定位的比较准。清空Dom断点最后的最后由本人水平所限，难免有错误以及不足之处， 屏幕前的靓仔靓女们 如有发现，恳请指出！你轻轻地点了个赞，那将在我的心里世界增添一颗明亮而耀眼的星！. 通过本地运行js代码那 实现脱离浏览器后 能够实现和浏览器上运行加密js的效果。网站上完全都是JavaScript实现的加密，我们的目的要知道加密的整个过程，并且实现这个加密的过程，拿到和浏览器一样的加密的结果。得到加密的结果之后就可以跳过浏览器，本地直接给服务器发送加密数据，从而直接获取服务器响应的结果。. 页面中有很多事件，比如说鼠标按下，滚动条滑动。最后的最后由本人水平所限，难免有错误以及不足之处， 屏幕前的靓仔靓女们 如有发现，恳请指出！你轻轻地点了个赞，那将在我的心里世界增添一颗明亮而耀眼的星！.

日常的web自动化过程中，我们常常用python selenium库来操纵Chrome浏览器实现网页的自动化。这其中有个比较头疼的问题：Chrome的更新频率非常频繁，与之对应的Chromedriver版本也必须相应更新。如果两者版本的主版本号相差超过1，selenium则会报异常. 如何在实体手机上，保证手机能够正常运行uiautomator2，并安装ATX-agent。以小米手机为例子，首先打开 设置-更多设置-开启开发者模式。如果初始化完成后，发现手机并没有安装ATXagent应用。说明设备未认证（unauthorized），此时，当你看到这个，就说明手机安装成功了环境。需要记得，将 USB安装 勾选上。. TA创建的收藏夹 TA关注的收藏夹. RGB颜色，例如： AFAFAF. 预览 取消 提交. 上一步 保存. 博客 资源 收藏 关注. 只看原创 排序： 按最后发布时间 按访问量 RSS订阅. 原创 Python量化交易实战教程汇总 B站配套视频教程观看设计适合自己并能适应市场的交易策略，才是量化交易的灵魂课程亲手带你设计并实现两种交易策略，快速培养你的策略思维能力择时策略：通过这个策略学会如何利用均线，创建择时策略，优化股票买入卖出的时间点。选股策略：掌握选股策略的核心逻辑，并基于收益率创建动量选股策略，并验证其有效性。手把手带你打造一个易扩展、更安全、效率更高的量化交易系统第三方平台大而全，不易扩展，效率还差，信息安全也是大问题，打造自己的交易平台才是更优解所有文章目录Python量化交易实战双均线策略股 原创 Js逆向教程AST Babel插件最简单修改值示例 最后的最后由本人水平所限，难免有错误以及不足之处， 屏幕前的靓仔靓女们 如有发现，恳请指出！你轻轻地点了个赞，那将在我的心里世界增添一颗明亮而耀眼的星！ 原创 Js逆向教程vscode无环境联调 最后的最后由本人水平所限，难免有错误以及不足之处， 屏幕前的靓仔靓女们 如有发现，恳请指出！你轻轻地点了个赞，那将在我的心里世界增添一颗明亮而耀眼的星！ 原创 Js逆向教程Hook基础 Hook就是在这些流程任意环节插入自己的代码，让浏览器先执行自己的代码 然后再执行原本网站的hook在以下流程中可以做的事情：hook在以下流程中可以做的事情上下文:表示一个环境（js上下文就是v8引擎，浏览器是不同的页签就是不同的上下文，js中的eval还是在一个上下文。只是虚拟机、）作用域:控制变量所生效的位置。作用域是更小的一个级别 处于上下文中结果如下：解释器是如何处理这段代码：首先解释器知道var xuhss在内存中声明了一个全局变量数组保存了xuhss，以后用的话，就到这个数组中找。如果数 php请求 原创 Js逆向教程websocket介绍 Ws和Wss的区别相当于http和https的区别，如果你想写一个聊天页面，需要频繁请求后台接口 还需要设置间隔时间（每隔1s发送一个请求） 才能拿到后台服务器的数据，因为http是轮询方式，只有请求完成后，才能拿到结果，只有客户端能发请求，所以说 要轮询。缺点就是占用服务器的性能？更好的方案就是websocket，它是浏览器实现的。浏览器在底层升级http协议，从http协议升级到websocket只需要添加几个头部信息就可以完成升级。 1.

原创 Js逆向教程极验滑块 实现加密算法的逻辑 还是和上节课一样，针对这个网址。 原创 Js逆向教程极验滑块 找到w加密位置 最后的最后由本人水平所限，难免有错误以及不足之处， 屏幕前的靓仔靓女们 如有发现，恳请指出！你轻轻地点了个赞，那将在我的心里世界增添一颗明亮而耀眼的星！ 原创 Js逆向教程滑块流程 极验 HTML5 的 canvas 元素使用 JavaScript 在网页上绘制图像。画布是一个矩形区域，您可以控制其每一像素。就是位图操作，可以理解为一个画图工具。可以任意对每个像素点进行任意操作之前讲解有一种断点类型叫做 事件监听断点，里面可以对canvas进行监听CanvasCreate canvas context 创建事件都选创建事件断点后，再刷页面断在这个地方：这里的代码用了流程平坦化打乱了最后的最后。 原创 Js逆向教程反调试 将你的预期值和实际值进行比较，如果不一样，就是这种debugger 只能通过浏览器调用的堆栈区分出正确的逻辑。通过将editbreakpoint设置为false 可以禁用这个调试。通过hook方式，将运行的函数设为空就可以跳过debugger了。最好的方式就是不要被识别出来调试，可以通过下hook解决。非虚拟机的方式不会跳转 到一个vm的页面。在eval里面运行debugger.

原创 Js逆向教程FuckJs 我们的目的为了让js代码运行起来。可以不需要解密，将代码扣出来运行就可以。任何一个js类型的变量结果 加上一个字符串 ，只会变成字符串。所以这个调试起来很麻烦 只能单步调试 还是用解密工具解密。通过这种特性 可以组合成各种各样的加密方式。这个的原理就是将各种字符串加起来。2个值通过 运算会变成0或者1.

jsfuck有对应的解密工具及。我们这里只是讲解js的混淆机制。可以看到只有这3种字符。 原创 Js逆向教程常见混淆AA和JJ js默认 支持Unicode的。所以支持所有的国家语种。有没有哪些国家的和O很像但不是O,和0很像但不是0,和p很像但不是p所以可以用这个相近的符号进行代码混淆。 原创 Js逆向教程常见代码混淆 最后的最后由本人水平所限，难免有错误以及不足之处， 屏幕前的靓仔靓女们 如有发现，恳请指出！你轻轻地点了个赞，那将在我的心里世界增添一颗明亮而耀眼的星！ 原创 Js逆向教程常见的加密方式 最后的最后由本人水平所限，难免有错误以及不足之处， 屏幕前的靓仔靓女们 如有发现，恳请指出！你轻轻地点了个赞，那将在我的心里世界增添一颗明亮而耀眼的星！

Please check back soon for future events, and sign up to receive invitations to our events and briefings. December 1, Speaker Series on California's Future — Virtual Event. November 30, Virtual Event. November 18, Annual Water Conference — In-Person and Online. We believe in the power of good information to build a brighter future for California. Help support our mission. Mark Baldassare , Dean Bonner , Rachel Lawler , and Deja Thomas. Supported with funding from the Arjay and Frances F.

Miller Foundation and the James Irvine Foundation. California voters have now received their mail ballots, and the November 8 general election has entered its final stage. Amid rising prices and economic uncertainty—as well as deep partisan divisions over social and political issues—Californians are processing a great deal of information to help them choose state constitutional officers and state legislators and to make policy decisions about state propositions. The midterm election also features a closely divided Congress, with the likelihood that a few races in California may determine which party controls the US House.

These are among the key findings of a statewide survey on state and national issues conducted from October 14 to 23 by the Public Policy Institute of California:. Today, there is a wide partisan divide: seven in ten Democrats are optimistic about the direction of the state, while 91 percent of Republicans and 59 percent of independents are pessimistic.

Californians are much more pessimistic about the direction of the country than they are about the direction of the state.

Majorities across all demographic groups and partisan groups, as well as across regions, are pessimistic about the direction of the United States. A wide partisan divide exists: most Democrats and independents say their financial situation is about the same as a year ago, while solid majorities of Republicans say they are worse off. Regionally, about half in the San Francisco Bay Area and Los Angeles say they are about the same, while half in the Central Valley say they are worse off; residents elsewhere are divided between being worse off and the same.

The shares saying they are worse off decline as educational attainment increases. Strong majorities across partisan groups feel negatively, but Republicans and independents are much more likely than Democrats to say the economy is in poor shape. Today, majorities across partisan, demographic, and regional groups say they are following news about the gubernatorial election either very or fairly closely.

In the upcoming November 8 election, there will be seven state propositions for voters. Due to time constraints, our survey only asked about three ballot measures: Propositions 26, 27, and For each, we read the proposition number, ballot, and ballot label.

Two of the state ballot measures were also included in the September survey Propositions 27 and 30 , while Proposition 26 was not. This measure would allow in-person sports betting at racetracks and tribal casinos, requiring that racetracks and casinos offering sports betting make certain payments to the state to support state regulatory costs. It also allows roulette and dice games at tribal casinos and adds a new way to enforce certain state gambling laws.

Fewer than half of likely voters say the outcome of each of these state propositions is very important to them. Today, 21 percent of likely voters say the outcome of Prop 26 is very important, 31 percent say the outcome of Prop 27 is very important, and 42 percent say the outcome of Prop 30 is very important. Today, when it comes to the importance of the outcome of Prop 26, one in four or fewer across partisan groups say it is very important to them.

About one in three across partisan groups say the outcome of Prop 27 is very important to them. Fewer than half across partisan groups say the outcome of Prop 30 is very important to them. When asked how they would vote if the election for the US House of Representatives were held today, 56 percent of likely voters say they would vote for or lean toward the Democratic candidate, while 39 percent would vote for or lean toward the Republican candidate. Democratic candidates are preferred by a point margin in Democratic-held districts, while Republican candidates are preferred by a point margin in Republican-held districts.

Abortion is another prominent issue in this election. When asked about the importance of abortion rights, 61 percent of likely voters say the issue is very important in determining their vote for Congress and another 20 percent say it is somewhat important; just 17 percent say it is not too or not at all important.

With the controlling party in Congress hanging in the balance, 51 percent of likely voters say they are extremely or very enthusiastic about voting for Congress this year; another 29 percent are somewhat enthusiastic while 19 percent are either not too or not at all enthusiastic.

Today, Democrats and Republicans have about equal levels of enthusiasm, while independents are much less likely to be extremely or very enthusiastic.

As Californians prepare to vote in the upcoming midterm election, fewer than half of adults and likely voters are satisfied with the way democracy is working in the United States—and few are very satisfied. Satisfaction was higher in our February survey when 53 percent of adults and 48 percent of likely voters were satisfied with democracy in America. Today, half of Democrats and about four in ten independents are satisfied, compared to about one in five Republicans.

Notably, four in ten Republicans are not at all satisfied. In addition to the lack of satisfaction with the way democracy is working, Californians are divided about whether Americans of different political positions can still come together and work out their differences.

Forty-nine percent are optimistic, while 46 percent are pessimistic. Today, in a rare moment of bipartisan agreement, about four in ten Democrats, Republicans, and independents are optimistic that Americans of different political views will be able to come together.

Notably, in , half or more across parties, regions, and demographic groups were optimistic. Today, about eight in ten Democrats—compared to about half of independents and about one in ten Republicans—approve of Governor Newsom.

Across demographic groups, about half or more approve of how Governor Newsom is handling his job. Approval of Congress among adults has been below 40 percent for all of after seeing a brief run above 40 percent for all of Democrats are far more likely than Republicans to approve of Congress. Fewer than half across regions and demographic groups approve of Congress.

Approval in March was at 44 percent for adults and 39 percent for likely voters. Across demographic groups, about half or more approve among women, younger adults, African Americans, Asian Americans, and Latinos. Views are similar across education and income groups, with just fewer than half approving. Approval in March was at 41 percent for adults and 36 percent for likely voters. Across regions, approval reaches a majority only in the San Francisco Bay Area.

Across demographic groups, approval reaches a majority only among African Americans. This map highlights the five geographic regions for which we present results; these regions account for approximately 90 percent of the state population. Residents of other geographic areas in gray are included in the results reported for all adults, registered voters, and likely voters, but sample sizes for these less-populous areas are not large enough to report separately.

The PPIC Statewide Survey is directed by Mark Baldassare, president and CEO and survey director at the Public Policy Institute of California. Coauthors of this report include survey analyst Deja Thomas, who was the project manager for this survey; associate survey director and research fellow Dean Bonner; and survey analyst Rachel Lawler. The Californians and Their Government survey is supported with funding from the Arjay and Frances F.

Findings in this report are based on a survey of 1, California adult residents, including 1, interviewed on cell phones and interviewed on landline telephones. The sample included respondents reached by calling back respondents who had previously completed an interview in PPIC Statewide Surveys in the last six months. Interviews took an average of 19 minutes to complete. Interviewing took place on weekend days and weekday nights from October 14—23, Cell phone interviews were conducted using a computer-generated random sample of cell phone numbers.

Additionally, we utilized a registration-based sample RBS of cell phone numbers for adults who are registered to vote in California. All cell phone numbers with California area codes were eligible for selection. After a cell phone user was reached, the interviewer verified that this person was age 18 or older, a resident of California, and in a safe place to continue the survey e. Cell phone respondents were offered a small reimbursement to help defray the cost of the call.

Cell phone interviews were conducted with adults who have cell phone service only and with those who have both cell phone and landline service in the household. Landline interviews were conducted using a computer-generated random sample of telephone numbers that ensured that both listed and unlisted numbers were called. Additionally, we utilized a registration-based sample RBS of landline phone numbers for adults who are registered to vote in California.

All landline telephone exchanges in California were eligible for selection. For both cell phones and landlines, telephone numbers were called as many as eight times. When no contact with an individual was made, calls to a number were limited to six. Also, to increase our ability to interview Asian American adults, we made up to three additional calls to phone numbers estimated by Survey Sampling International as likely to be associated with Asian American individuals.

Accent on Languages, Inc. The survey sample was closely comparable to the ACS figures. To estimate landline and cell phone service in California, Abt Associates used state-level estimates released by the National Center for Health Statistics—which used data from the National Health Interview Survey NHIS and the ACS.

The estimates for California were then compared against landline and cell phone service reported in this survey. We also used voter registration data from the California Secretary of State to compare the party registration of registered voters in our sample to party registration statewide.

The sampling error, taking design effects from weighting into consideration, is ±3. This means that 95 times out of , the results will be within 3. The sampling error for unweighted subgroups is larger: for the 1, registered voters, the sampling error is ±4. For the sampling errors of additional subgroups, please see the table at the end of this section. Sampling error is only one type of error to which surveys are subject.

Results may also be affected by factors such as question wording, question order, and survey timing. We present results for five geographic regions, accounting for approximately 90 percent of the state population.

Residents of other geographic areas are included in the results reported for all adults, registered voters, and likely voters, but sample sizes for these less-populous areas are not large enough to report separately.

We also present results for congressional districts currently held by Democrats or Republicans, based on residential zip code and party of the local US House member. We compare the opinions of those who report they are registered Democrats, registered Republicans, and no party preference or decline-to-state or independent voters; the results for those who say they are registered to vote in other parties are not large enough for separate analysis.

We also analyze the responses of likely voters—so designated per their responses to survey questions about voter registration, previous election participation, intentions to vote this year, attention to election news, and current interest in politics. The percentages presented in the report tables and in the questionnaire may not add to due to rounding. Additional details about our methodology can be found at www.

pdf and are available upon request through surveys ppic. October 14—23, 1, California adult residents; 1, California likely voters English, Spanish. Margin of error ±3.

Could not load branches. The signal conditioner is in charge of resampling the signal and delivering a reference sample rate to the downstream processing blocks, acting as a facade between the signal source and the synchronization channels, providing a simplified interface to the input signal. URLs in many places in the package documentation will be converted to clickable hyperlinks in at least some of their renderings. The use of conditional execution on chips where it is available is controlled by -fif-conversion2. The maximum number of insns in a region to be considered for pipelining in the selective scheduler.

Categories:

• Forex
• Binary Options
• Binary Options online
• Forex Bitcoin
• Forex Brokers