dpkg-source(1) dpkg utilities dpkg-source(1) NAME dpkg-source - Debian source package (.dsc) manipulation tool SYNOPSIS dpkg-source [option...] command DESCRIPTION dpkg-source packs and unpacks Debian source archives. None of these commands allow multiple options to be combined into one, and they do not allow the value for an option to be specified in a sepa‐ rate argument. COMMANDS -x filename.dsc [output-directory] Extract a source package. One non-option argument must be sup‐ plied, the name of the Debian source control file (.dsc). An optional second non-option argument may be supplied to specify the directory to extract the source package to, this must not exist. If no output directory is specified, the source package is extracted into a directory named source-version under the current working directory. dpkg-source will read the names of the other file(s) making up the source package from the control file; they are assumed to be in the same directory as the .dsc. The files in the extracted package will have their permissions and ownerships set to those which would have been expected if the files and directories had simply been created - directories and executable files will be 0777 and plain files will be 0666, both modified by the extractors' umask; if the parent directory is set‐ gid then the extracted directories will be too, and all the files and directories will inherit its group ownership. If the source package uses a non-standard format (currently this means all formats except "1.0"), its name will be stored in debian/source/format so that the following builds of the source package use the same format by default. -b directory [format-specific-parameters] Build a source package. The first non-option argument is taken as the name of the directory containing the debianized source tree (i.e. with a debian sub-directory and maybe changes to the origi‐ nal files). Depending on the source package format used to build the package, additional parameters might be accepted. dpkg-source will build the source package with the first format found in this ordered list: the format indicated with the --format command line option, the format indicated in debian/source/format, "1.0". The fallback to "1.0" is deprecated and will be removed at some point in the future, you should always document the desired source format in debian/source/format. See section SOURCE PACKAGE FORMATS for an extensive description of the various source package formats. --print-format directory Print the source format that would be used to build the source package if dpkg-source -b directory was called (in the same condi‐ tions and with the same parameters). --before-build directory Run the corresponding hook of the source package format. This hook is called before any build of the package (dpkg-buildpackage calls it very early even before debian/rules clean). This command is idempotent and can be called multiple times. Not all source for‐ mats implement something in this hook, and those that do usually prepare the source tree for the build for example by ensuring that the Debian patches are applied. --after-build directory Run the corresponding hook of the source package format. This hook is called after any build of the package (dpkg-buildpackage calls it last). This command is idempotent and can be called multiple times. Not all source formats implement something in this hook, and those that do usually use it to undo what --before-build has done. --commit [directory] ... Record changes in the source tree unpacked in directory. This com‐ mand can take supplementary parameters depending on the source format. It will error out for formats where this operation doesn't mean anything. -?, --help Show the usage message and exit. --version Show the version and exit. GENERIC BUILD OPTIONS -ccontrol-file Specifies the main source control file to read information from. The default is debian/control. If given with relative pathname this is interpreted starting at the source tree's top level direc‐ tory. -lchangelog-file Specifies the changelog file to read information from. The default is debian/changelog. If given with relative pathname this is interpreted starting at the source tree's top level directory. -Fchangelog-format Specifies the format of the changelog. See dpkg-parsechangelog(1) for information about alternative formats. --format=value Use the given format for building the source package. It does override any format given in debian/source/format. -Vname=value Set an output substitution variable. See deb-substvars(5) for a discussion of output substitution. -Tsubstvars-file Read substitution variables in substvars-file; the default is to not read any file. This option can be used multiple times to read substitution variables from multiple files. -Dfield=value Override or add an output control file field. -Ufield Remove an output control file field. -Zcompression, --compression=compression Specify the compression to use for created files (tarballs and diffs). Note that this option will not cause existing tarballs to be recompressed, it only affects new files. Supported values are: gzip, bzip2, lzma and xz. gzip is the default. xz is only sup‐ ported since dpkg-dev 1.15.5. -zlevel, --compression-level=level Compression level to use. As with -Z it only affects newly created files. Supported values are: 1 to 9, best, and fast. The default is 9 for gzip and bzip2, 6 for xz and lzma. -i[regexp], --diff-ignore[=regexp] You may specify a perl regular expression to match files you want filtered out of the list of files for the diff. (This list is gen‐ erated by a find command.) (If the source package is being built as a version 3 source package using a VCS, this can be used to ignore uncommited changes on specific files. Using -i.* will ignore all of them.) -i by itself enables the option, with a default regexp that will filter out control files and directories of the most common revision control systems, backup and swap files and Libtool build output directories. There can only be one active regexp, of multiple -i options only the last one will take effect. This is very helpful in cutting out extraneous files that get included in the diff, e.g. if you maintain your source in a revi‐ sion control system and want to use a checkout to build a source package without including the additional files and directories that it will usually contain (e.g. CVS/, .cvsignore, .svn/). The default regexp is already very exhaustive, but if you need to replace it, please note that by default it can match any part of a path, so if you want to match the begin of a filename or only full filenames, you will need to provide the necessary anchors (e.g. '(^|/)', '($|/)') yourself. --extend-diff-ignore=regexp The perl regular expression specified will extend the default value of --diff-ignore and its current value (if set). It does this by concatenating "|regexp" to the existing value. This option is convenient to use in debian/source/options to exclude some auto-generated files from the automatic patch generation. -I[file-pattern], --tar-ignore[=file-pattern] If this option is specified, the pattern will be passed to tar(1)'s --exclude option when it is called to generate a .orig.tar or .tar file. For example, -ICVS will make tar skip over CVS directories when generating a .tar.gz file. The option may be repeated multiple times to list multiple patterns to exclude. -I by itself adds default --exclude options that will filter out control files and directories of the most common revision control systems, backup and swap files and Libtool build output directo‐ ries. Note: While they have similar purposes, -i and -I have very different syntax and semantics. -i can only be specified once and takes a perl com‐ patible regular expression which is matched against the full relative path of each file. -I can specified multiple times and takes a filename pattern with shell wildcards. The pattern is applied to the full rela‐ tive path but also to each part of the path individually. The exact semantic of tar's --exclude option is somewhat complicated, see http://www.gnu.org/software/tar/manual/tar.html#wildcards for a full doc‐ umentation. The default regexp and patterns for both options can be seen in the out‐ put of the --help command. GENERIC EXTRACT OPTIONS --no-copy Do not copy original tarballs near the extracted source package. --no-check Do not check signatures and checksums before unpacking. --require-valid-signature Refuse to unpack the source package if it doesn't contain an OpenPGP signature that can be verified either with the user's trustedkeys.gpg keyring, one of the vendor-specific keyrings, or one of the official Debian keyrings (/usr/share/keyrings/debian-keyring.gpg and /usr/share/keyrings/debian-maintainers.gpg). SOURCE PACKAGE FORMATS If you don't know what source format to use, you should probably pick either "3.0 (quilt)" or "3.0 (native)". See http://wiki.debian.org/Projects/DebSrc3.0 for information on the deploy‐ ment of those formats within Debian. Format: 1.0 A source package in this format consists either of a .orig.tar.gz associ‐ ated to a .diff.gz or a single .tar.gz (in that case the package is said to be native). Extracting Extracting a native package is a simple extraction of the single tarball in the target directory. Extracting a non-native package is done by first unpacking the .orig.tar.gz and then applying the patch contained in the .diff.gz file. The timestamp of all patched files is reset to the extrac‐ tion time of the source package (this avoids timestamp skews leading to problems when autogenerated files are patched). The diff can create new files (the whole debian directory is created that way) but can't remove files (empty files will be left over). Building Building a native package is just creating a single tarball with the source directory. Building a non-native package involves extracting the original tarball in a separate ".orig" directory and regenerating the .diff.gz by comparing the source package directory with the .orig direc‐ tory. Build options (with -b): If a second non-option argument is supplied it should be the name of the original source directory or tarfile or the empty string if the package is a Debian-specific one and so has no Debianisation diffs. If no second argument is supplied then dpkg-source will look for the original source tarfile package_upstream-version.orig.tar.gz or the original source directory directory.orig depending on the -sX arguments. -sa, -sp, -sk, -su and -sr will not overwrite existing tarfiles or direc‐ tories. If this is desired then -sA, -sP, -sK, -sU and -sR should be used instead. -sk Specifies to expect the original source as a tarfile, by default package_upstream-version.orig.tar.extension. It will leave this original source in place as a tarfile, or copy it to the current directory if it isn't already there. The tarball will be unpacked into directory.orig for the generation of the diff. -sp Like -sk but will remove the directory again afterwards. -su Specifies that the original source is expected as a directory, by default package-upstream-version.orig and dpkg-source will create a new original source archive from it. -sr Like -su but will remove that directory after it has been used. -ss Specifies that the original source is available both as a direc‐ tory and as a tarfile. dpkg-source will use the directory to cre‐ ate the diff, but the tarfile to create the .dsc. This option must be used with care - if the directory and tarfile do not match a bad source archive will be generated. -sn Specifies to not look for any original source, and to not generate a diff. The second argument, if supplied, must be the empty string. This is used for Debian-specific packages which do not have a separate upstream source and therefore have no debianisa‐ tion diffs. -sa or -sA Specifies to look for the original source archive as a tarfile or as a directory - the second argument, if any, may be either, or the empty string (this is equivalent to using -sn). If a tarfile is found it will unpack it to create the diff and remove it after‐ wards (this is equivalent to -sp); if a directory is found it will pack it to create the original source and remove it afterwards (this is equivalent to -sr); if neither is found it will assume that the package has no debianisation diffs, only a straightfor‐ ward source archive (this is equivalent to -sn). If both are found then dpkg-source will ignore the directory, overwriting it, if -sA was specified (this is equivalent to -sP) or raise an error if -sa was specified. -sA is the default. --abort-on-upstream-changes The process fails if the generated diff contains changes to files outside of the debian sub-directory. This option is not allowed in debian/source/options but can be used in debian/source/local-options. Extract options (with -x): In all cases any existing original source tree will be removed. -sp Used when extracting then the original source (if any) will be left as a tarfile. If it is not already located in the current directory or if an existing but different file is there it will be copied there. (This is the default). -su Unpacks the original source tree. -sn Ensures that the original source is neither copied to the current directory nor unpacked. Any original source tree that was in the current directory is still removed. All the -sX options are mutually exclusive. If you specify more than one only the last one will be used. --skip-debianization Skips application of the debian diff on top of the upstream sources. Format: 2.0 Also known as wig&pen. This format is not recommended for wide-spread usage, the format "3.0 (quilt)" replaces it. Wig&pen was the first speci‐ fication of a new-generation source package format. The behaviour of this format is the same as the "3.0 (quilt)" format except that it doesn't use an explicit list of patches. All files in debian/patches/ matching the perl regular expression [\w-]+ must be valid patches: they are applied at extraction time. When building a new source package, any change to the upstream source is stored in a patch named zz_debian-diff-auto. Format: 3.0 (native) This format is an extension of the native package format as defined in the 1.0 format. It supports all compression methods and will ignore by default any VCS specific files and directories as well as many temporary files (see default value associated to -I option in the --help output). Format: 3.0 (quilt) A source package in this format contains at least an original tarball (.orig.tar.ext where ext can be gz, bz2, lzma and xz) and a debian tar‐ ball (.debian.tar.ext). It can also contain additional original tarballs (.orig-component.tar.ext). component can only contain alphanumeric char‐ acters and dashes ("-"). Extracting The main original tarball is extracted first, then all additional origi‐ nal tarballs are extracted in subdirectories named after the component part of their filename (any pre-existing directory is replaced). The debian tarball is extracted on top of the source directory after prior removal of any pre-existing debian directory. Note that the debian tar‐ ball must contain a debian sub-directory but it can also contain binary files outside of that directory (see --include-binaries option). All patches listed in debian/patches/debian.series or debian/patches/series are then applied. If the former file is used and the latter one doesn't exist (or is a symlink), then the latter is replaced with a symlink to the former. This is meant to simplify usage of quilt to manage the set of patches. Note however that while dpkg-source parses correctly series files with explicit options used for patch appli‐ cation (stored on each line after the patch filename and one or more spa‐ ces), it does ignore those options and always expect patches that can be applied with the -p1 option of patch. It will thus emit a warning when it encounters such options, and the build is likely to fail. Contrary to quilt's default behaviour, patches are expected to apply without any fuzz. When that is not the case, you should refresh such patches with quilt, or dpkg-source will error out while trying to apply them. Similarly to quilt's default behaviour, the patches can remove files too. The file .pc/applied-patches is created if some patches have been applied during the extraction. Building All original tarballs found in the current directory are extracted in a temporary directory by following the same logic as for the unpack, the debian directory is copied over in the temporary directory, and all patches except the automatic patch (debian-changes-version or debian-changes, depending on --single-debian-patch) are applied. The tem‐ porary directory is compared to the source package directory. When the diff is non-empty, the build fails unless --single-debian-patch or --auto-commit has been used, in which case the diff is stored in the automatic patch. If the automatic patch is created/deleted, it's added/removed from the series file and from the quilt metadata. Any change on a binary file is not representable in a diff and will thus lead to a failure unless the maintainer deliberately decided to include that modified binary file in the debian tarball (by listing it in debian/source/include-binaries). The build will also fail if it finds binary files in the debian sub-directory unless they have been whitelisted through debian/source/include-binaries. The updated debian directory and the list of modified binaries is then used to generate the debian tarball. The automatically generated diff doesn't include changes on VCS specific files as well as many temporary files (see default value associated to -i option in the --help output). In particular, the .pc directory used by quilt is ignored during generation of the automatic patch. Note: dpkg-source --before-build (and -b) will ensure that all patches listed in the series file are applied so that a package build always has all patches applied. It does this by finding unapplied patches (they are listed in the series file but not in .pc/applied-patches), and if the first patch in that set can be applied without errors, it will apply them all. The option --no-preparation can be used to disable this behavior. Recording changes --commit [directory] [patch-name] [patch-file] Generates a patch corresponding to the local changes that are not managed by the quilt patch system and integrates it in the patch system under the name patch-name. If the name is missing, it will be asked interactively. If patch-file is given, it is used as the patch corresponding to the local changes to integrate. Once inte‐ grated, an editor is launched so that you can edit the meta-infor‐ mation in the patch header. Passing patch-file is mainly useful after a build failure that pre-generated this file, and on this ground the given file is removed after integration. Note also that the changes contained in the patch file must already be applied on the tree and that the files modified by the patch must not have supplementary unrecorded changes. If the patch generation detects modified binary files, they will be automatically added to debian/source/include-binaries so that they end up in the debian tarball (exactly like dpkg-source --include-binaries -b would do). Build options --allow-version-of-quilt-db=version Allow dpkg-source to build the source package if the version of the quilt metadata is the one specified, even if dpkg-source doesn't know about it. Effectively this says that the given ver‐ sion of the quilt metadata is compatible with the version 2 that dpkg-source currently supports. The version of the quilt metadata is stored in .pc/.version. --include-removal Do not ignore removed files and include them in the automatically generated patch. --include-timestamp Include timestamp in the automatically generated patch. --include-binaries Add all modified binaries in the debian tarball. Also add them to debian/source/include-binaries: they will be added by default in subsequent builds and this option is thus no more needed. --no-preparation Do not try to prepare the build tree by applying patches which are apparently unapplied. --single-debian-patch Use debian/patches/debian-changes instead of debian/patches/debian-changes-version for the name of the auto‐ matic patch generated during build. This option is particularly useful when the package is maintained in a VCS and a patch set can't reliably be generated. Instead the current diff with upstream should be stored in a single patch. The option would be put in debian/source/local-options and would be accompanied by a debian/source/local-patch-header file explaining how the Debian changes can be best reviewed, for example in the VCS that is used. --create-empty-orig Automatically create the main original tarball as empty if it's missing and if there are supplementary original tarballs. This option is meant to be used when the source package is just a bun‐ dle of multiple upstream software and where there's no "main" software. --no-unapply-patches, --unapply-patches By default, dpkg-source will automatically unapply the patches in the --after-build hook if it did apply them during --before-build. Those options allow you to forcefully disable or enable the patch unapplication process. Those options are only allowed in debian/source/local-options so that all generated source packages have the same behavior by default. --abort-on-upstream-changes The process fails if an automatic patch has been generated. This option can be used to ensure that all changes were properly recorded in separate quilt patches prior to the source package build. This option is not allowed in debian/source/options but can be used in debian/source/local-options. --auto-commit The process doesn't fail if an automatic patch has been generated, instead it's immediately recorded in the quilt series. Extract options --skip-debianization Skips extraction of the debian tarball on top of the upstream sources. --skip-patches Do not apply patches at the end of the extraction. Format: 3.0 (custom) This format is special. It doesn't represent a real source package format but can be used to create source packages with arbitrary files. Build options All non-option arguments are taken as files to integrate in the generated source package. They must exist and are preferably in the current direc‐ tory. At least one file must be given. --target-format=value Required. Defines the real format of the generated source package. The generated .dsc file will contain this value in its Format field and not "3.0 (custom)". Format: 3.0 (git) This format is experimental. A source package in this format consists of a single bundle of a git repository .git to hold the source of a package. There may also be a .gitshallow file listing revisions for a shallow git clone. Extracting The bundle is cloned as a git repository to the target directory. If there is a gitshallow file, it is installed as `.git/shallow` inside the cloned git repository. Note that by default the new repository will have the same branch checked out that was checked out in the original source. (Typically "master", but it could be anything.) Any other branches will be available under `remotes/origin/`. Building Before going any further, some checks are done to ensure that we don't have any non-ignored uncommitted changes. git-bundle(1) is used to generate a bundle of the git repository. By default, all branches and tags in the repository are included in the bun‐ dle. Build options --git-ref=ref Allows specifying a git ref to include in the git bundle. Use dis‐ ables the default behavior of including all branches and tags. May be specified multiple times. The ref can be the name of a branch or tag to include. It may also be any parameter that can be passed to git-rev-list(1). For example, to include only the master branch, use --git-ref=master. To include all tags and branches, except for the private branch, use --git-ref=--all --git-ref=^pri‐ vate --git-depth=number Creates a shallow clone with a history truncated to the specified number of revisions. Format: 3.0 (bzr) This format is experimental. It generates a single tarball containing the bzr repository. Extracting The tarball is unpacked and then bzr is used to checkout the current branch. Building Before going any further, some checks are done to ensure that we don't have any non-ignored uncommitted changes. Then the VCS specific part of the source directory is copied over to a temporary directory. Before this temporary directory is packed in a tar‐ ball, various cleanup are done to save space. WARNINGS AND ERRORS no source format specified in debian/source/format The file debian/source/format should always exist and indicate the desired source format. For backwards compatibility, format "1.0" is assumed when the file doesn't exist but you should not rely on this: at some point in the future dpkg-source will be modified to fail when that file doesn't exist. The rationale is that format "1.0" is no longer the recommended format, you should usually pick one of the newer formats ("3.0 (quilt)", "3.0 (native)") but dpkg-source will not do this automatically for you. If you want to continue using the old format, you should be explicit about it and put "1.0" in debian/source/format. the diff modifies the following upstream files When using source format "1.0" it is usually a bad idea to modify upstream files directly as the changes end up hidden and mostly undocu‐ mented in the .diff.gz file. Instead you should store your changes as patches in the debian directory and apply them at build-time. To avoid this complexity you can also use the format "3.0 (quilt)" that offers this natively. cannot represent change to file Changes to upstream sources are usually stored with patch files, but not all changes can be represented with patches: they can only alter the con‐ tent of plain text files. If you try replacing a file with something of a different type (for example replacing a plain file with a symlink or a directory), you will get this error message. newly created empty file file will not be represented in diff Empty files can't be created with patch files. Thus this change is not recorded in the source package and you are warned about it. executable mode perms of file will not be represented in diff special mode perms of file will not be represented in diff Patch files do not record permissions of files and thus modified permis‐ sions are not stored in the source package. This warning reminds you of that fact. FILE FORMATS debian/source/format This file contains on a single line the format that should be used to build the source package (possible formats are described above). No lead‐ ing or trailing spaces are allowed. debian/source/include-binaries This file contains a list of binary files (one per line) that should be included in the debian tarball. Leading and trailing spaces are stripped. Lines starting with "#" are comments and are skipped. Empty lines are ignored. debian/source/options This file contains a list of long options that should be automatically prepended to the set of command line options of a dpkg-source -b or dpkg-source --print-format call. Options like --compression and --com‐ pression-level are well suited for this file. Each option should be put on a separate line. Empty lines and lines starting with "#" are ignored. The leading "--" should be stripped and short options are not allowed. Optional spaces are allowed around the "=" symbol and optional quotes are allowed around the value. Here's an exam‐ ple of such a file: # let dpkg-source create a debian.tar.bz2 with maximal compression compression = "bzip2" compression-level = 9 # use debian/patches/debian-changes as automatic patch single-debian-patch # ignore changes on config.{sub,guess} extend-diff-ignore = "(^|/)(config.sub|config.guess)$" Note: format options are not accepted in this file, you should use debian/source/format instead. debian/source/local-options Exactly like debian/source/options except that the file is not included in the generated source package. It can be useful to store a preference tied to the maintainer or to the VCS repository where the source package is maintained. debian/source/local-patch-header debian/source/patch-header Free form text that is put on top of the automatic patch generated in formats "2.0" or "3.0 (quilt)". local-patch-header is not included in the generated source package while patch-header is. debian/patches/series This file lists all patches that have to be applied (in the given order) on top of the upstream source package. Leading and trailing spaces are stripped. Lines starting with "#" are comments and are skipped. Empty lines are ignored. Remaining lines start with a patch filename (relative to the debian/patches/ directory) up to the first space character or the end of line. Optional quilt options can follow up to the end of line or the first "#" preceded by one or more spaces (which marks the start of a comment up to the end of line). BUGS The point at which field overriding occurs compared to certain standard output field settings is rather confused. SEE ALSO dpkg-deb(1), dpkg(1), dselect(1). Debian Project 2012-05-04 dpkg-source(1)


You can configure Geode to write immediately to disk and you may be able to modify your operating system behavior to perform buffer flushes more frequently.
Typically, Geode writes disk data into the operating system’s disk buffers and the operating system periodically flushes the buffers to disk. Increasing the frequency of writes to disk decreases the likelihood of data loss from application or machine crashes, but it impacts performance. Your other option, which may give you better performance, is to use Geode’s in-memory data backups. Do this by storing your data in multiple replicated regions or in partitioned regions that are configured with redundant copies. See Region Types.
Modifying Disk Flushes for the Operating System
You may be able to change the operating system settings for periodic flushes. You may also be able to perform explicit disk flushes from your application code. For information on these options, see your operating system’s documentation. For example, in Linux you can change the disk flush interval by modifying the setting /proc/sys/vm/dirty_expire_centiseconds
. It defaults to 30 seconds. To alter this setting, see the Linux documentation for dirty_expire_centiseconds
.
Modifying Geode to Flush Buffers on Disk Writes
You can have Geode flush the disk buffers on every disk write. Do this by setting the system property gemfire.syncWrites
to true at the command line when you start your Geode member. You can only modify this setting when you start a member. When this is set, Geode uses a Java RandomAccessFile
with the flags “rwd”, which causes every file update to be written synchronously to the storage device.  See the Java documentation for java.IO.RandomAccessFile
.
To modify the setting for a Geode application, add this to the java command line when you start the member:
-Dgemfire.syncWrites=true
To modify the setting for a cache server, use this syntax:
gfsh>start server --name=... --J=-Dgemfire.syncWrites=true


Lack of Fit Test for Linear Regression
March 18, 2017
Myers et al. [1] provides a derivation for a simple lack of fit test in section 2.7. The derivation looks at whether or not a linear model of form
adequately describes the data. Unfortunately the example provided has a mistake (while the figure matches the data, the coefficients and error values do not), so this post aims to provide corrected error values for the sample data. In addition, all of the source code to work through the problem in Python is provided here.
In order to apply the lack of fit test, we’ll need a data set that has true replicates as described in [1]. The following figure contains the data set we’ll be working with, along with the linear model fit to the data.
The coefficients of the linear model that were determined with a least squares fit are \( \beta_0 =13.25847151, \beta_1 = 2.12367129 \). The Python code to generate the data, create the figure, and perform the least squares fit is available below.
As it happens, the data has \( n_i \) observations for each unique \( x_i\) level. For instance when \( x = 1.0 \), there are 2 observations of \(x\). However \( x= 2.0 \) only has 1 observation. The data has \( m \) number of levels. The residual sum of squares (the sum of squares of the residuals, in Python variable SSe returned from the linear regression) is then broken into two separate components such that
where \( SS_{PE} \) represents the sum of squares from pure error and \( SS_{LOF} \) represents the sum of squares from the lack of fit. The sum of squares from pure error is defined as
where \( y_{ij} \) is the j observation from the data at the \( x_i \) level where \( j = 1, \cdots, n_i \). Source code to calculate the sum of the squares due to pure error is provided below.
The sum of squares from lack of fit is defined as
where \( \bar{y}\) is the y mean of the i level and \( \hat{y}\) is the predicted y response at \( x_i \). The source code to calculate the sum of squares for the lack of fit is provided below.
We thus far have for this example that \(SS_{E} = 255.22, SS_{PE} = 17.20, SS_{LOF} = 238.02 \). It can be noted that the equation \( SS_E = SS_{PE} + SS_{LOF} \) holds true.
The test statistic \( F_0 \) to test for lack of fit is defined as
for \( p \) number of parameters. The code to calculate the test statistic is provided below.
We find that \( F_0 = 12.106 \) which follows the F-distribution of \( F(\alpha : m-p, n-m) \). It can be concluded that regression function is not linear because \( F_0 = 12.106 > F(\alpha : m-p, n-m) \). Alternatively the P-value for the hypothesis of \( P(F_0 \leq F(F_0: m-p, n-m) \) is 0.0018. Since the P-value is so small, the hypothesis is rejected. The P-value can be calculated with the following code:
In conclusion the linear model of \( \hat{y} = \beta_0 + \beta_1 x \) is inadequate of representing the data because most of the error results from the lack of fit, rather than pure error in the data. A better model can be constructed (potentially a higher order polynomial) to reduce the error from lack of fit.
[1] R. H. Myers, D. C. Montgomery, C. M. Anderson-Cook, Response Sur- face Methodology: Process and Product Optimization Using Designed Experiments, Wiley Series in Probability and Statistics, Wiley, ISBN<PHONE_NUMBER>032, 2016.


The New Survivalist
|
Are
You Defenseless Without A Firearm?
|
Probably every person
who has a carry permit in the United States has at least one other weapon
on them other than their pistol; I would be willing to bet it is a folding
knife. I would also bet that they have never practiced with their
folding knives and practice with their carry pistol extensively. In this
article I will go over what I believe to be some rather important facts
as to why you should also train with your knife that you carry as much as
you train with your pistol. First of all, I have read on countless forums
the argument that concealed carry is a lifestyle and the hardcore carriers
make habits of avoiding places that forbid civilians from carrying pistols
onto the premisses. This simply isn't possible. Here are just a few of the
places under federal and state laws where civilians cannot, under any circumstances,
carry a firearm: 1. Commercial airline travel 2. Work (Most employers will
not let their employees carry guns to work) 3. Government establishments
such as the DMV, courtrooms (Jury duty) and the post office 4. Colleges
and any sports games on campus 5. High schools and any sports games on campus
You see, the horrible thing about these laws is they make these places a
virtual turkey shoot to anybody who desires to go on a shooting spree. And
the truth is, civilians who take the carry permit class and fill out the
paper work pretend that they are now special and can somehow avoid places
were no civilian, one-day class taken or not, can step inside with a firearm.
These places are impossible to avoid for any member of our society. It is
a fact that any normal person of average health can travel about 7 yards
in 2 seconds with a contact weapon such as a knife. It takes a person who
trains with his pistol about 1.5 seconds to take the gun from the holster
aim and get off a shot or two on average. So unless you're very aware of
your surroundings and the person's attack cues, you are getting stabbed.

I'm not telling anyone to bring a knife to a gun fight, I'm just saying
I do not underestimate what a person is capable of with a knife. Especially
when they have trained with it. And here are some facts for the female audience
or those of you who have daughters. Women who are ages 16-19 statistically
are more likely to be the victims of violent crime than anyone else in this
country, with women ages 20-24 coming in second. Half of all the rapes in
the U.S happen to women under the age of 18. One third of rapes in the U.S
happen to women ages 12-17. To get a carry permit you have to be 21. So
by the time women are legally able to carry a pistol in public they have
passed the prime age for being attacked, raped, abducted or murdered. And
there are also the many fine politicians who represent us in Washington
D.C. who are dedicated to the disarmament of the American public.
What do you think would happen if policemen banged on your door and had M16's pointed at you and your family, one in the chamber, the safety off and ready to go?  I hope this never happens to anybody, but no gun owner in this country should believe it's not a likely they will encounter a situation similar to this in the near future. The best self defense training is combining baton and knife drills with your firearms training. This won't solve all your problems, but it drastically improves your self defense training. A good folding knife, baton, combat boots and a bulletproof vest can go a long way if you keep a low profile. Article by Rick Saxby |


Our Story
Spreading Holiday Cheer to local children in Need
The Campbell Community Toy Program works in conjunction with the Campbell Union School District Grades K-8 to provide toys, games and fun gifts for Christmas. This program serves low income families in our community and involves over 2300 children from over 800 families. Community volunteers join together to donate, gather, organize and distribute thousands of gifts through the program each year.
Spread the Word
Get Social!
Like & Share our Facebook page
Questions?
Contact toy drive coordinator with any questions


Django Stories 1.0.4 documentation
Three states are possible:
If Categories is integrated, you will see a Categories section.
In order to make publishing to different formats easier (such as RSS/Atom feeds, ePublications, web, and print for example), we don’t recommend placing media and other related content inside the story. Story relations are pieces of content that relate to a story in some way. These could be photos, galleries, movies, documents, and other stories for example. they make it easy to mark and relate objects to use differently, depending on the output destination.


Learn to Multiply
{{numb.number}}
All
Start
{{name || 'Kid'}} what is
{{left}} x {{right}} = ?
{{ opt }}
Problems: {{progress()}}
{{name || 'Kid'}} your score is:
{{ score }}
are you happy?
Play Again


The sax package implements a SAX (Simple API for XML) parser for HTML.
It uses the SAX 2 interfaces available from the sax project.
The HTML parser sax package is currently in it's infancy and just exposes the DOM Parser
via a SAX interface. The driver name is "org.htmlparser.sax.XMLReader" and a
simplistic test program is available in the org.htmlparser.tests package as
SAXTest.java.
Some major pieces are missing, like namespace support (HTML files won't
generally have much in the way of namespaces), attribute type info, resolvers
and DTD handlers, among many other things.


--- layout: post title: Fun with 82 - Auto create Location categories: [] tags: cm-82 status: publish type: post published: true meta: {} ---
A new and simple way to auto generate new Locations for authenticated users.


My Team
bob
Manager
ID: 12
Email:
<EMAIL_ADDRESS>Office Number: 214
bob
Engineer
ID: 13
Email:
<EMAIL_ADDRESS>GitHub:
bobsrepos
bob
Intern
ID: 14
Email:
<EMAIL_ADDRESS>School: GA Tech


--- title: Applies Dropout to the input. type: docs repo: https://github.com/rstudio/keras menu: main: name: Applies Dropout to the input. - keras parent: keras-reference aliases: - /reference/keras/layer_dropout.html - /keras/reference/layer_dropout.html - /guide/keras/reference/layer_dropout.html - /tools/tools/keras/reference/layer_dropout.html - /installation/keras/reference/layer_dropout.html - /tutorials/keras/reference/layer_dropout.html - /guide/tools/keras/reference/layer_dropout.html - /deploy/keras/reference/layer_dropout.html - /tools/keras/reference/layer_dropout.html - /tutorials/tools/keras/reference/layer_dropout.html ---
Dropout consists in randomly setting a fraction rate
of input units to 0 at
each update during training time, which helps prevent overfitting.
layer_dropout(
object,
rate,
noise_shape = NULL,
seed = NULL,
input_shape = NULL,
batch_input_shape = NULL,
batch_size = NULL,
name = NULL,
trainable = NULL,
weights = NULL
)
| object | Model or layer object |
| rate | float between 0 and 1. Fraction of the input units to drop. |
| noise_shape | 1D integer tensor representing the shape of the binary
dropout mask that will be multiplied with the input. For instance, if your
inputs have shape |
| seed | integer to use as random seed. |
| input_shape | Dimensionality of the input (integer) not including the samples axis. This argument is required when using this layer as the first layer in a model. |
| batch_input_shape | Shapes, including the batch size. For instance,
|
| batch_size | Fixed batch size for layer |
| name | An optional name string for the layer. Should be unique in a model (do not reuse the same name twice). It will be autogenerated if it isn't provided. |
| trainable | Whether the layer weights will be updated during training. |
| weights | Initial weights for layer. |
Other core layers:
layer_activation()
,
layer_activity_regularization()
,
layer_attention()
,
layer_dense_features()
,
layer_dense()
,
layer_flatten()
,
layer_input()
,
layer_lambda()
,
layer_masking()
,
layer_permute()
,
layer_repeat_vector()
,
layer_reshape()
Other dropout layers:
layer_spatial_dropout_1d()
,
layer_spatial_dropout_2d()
,
layer_spatial_dropout_3d()


I first heard about programming when I was preparing for my first test in the University as a Chemical Engineering student. Since then I have always known this is what I wanted to do. After a few months I changed my major to Computer Science.
My first computer science class was taught by the first female Computer Science professor in West Africa. She told us a story about a former student that was very good in Java. Fortunately I was already having a knack for JavaScript. That day I made the decision I will follow JavaScript with everything I have got.
Some years have passed and I have worked with various companies helping them scale their server, improving the quality of their codebase and helping them ship great products to the market as fast as possible. So, now, in industry, this passion remains with me. There's certainly yet more to learn, yet more problems to solve, and yet more to build. And for this, I am very grateful.
Aside from being at the front of my computer screen, I like to write about my life's view on medium .
This project aims to be the best platform for online interactions in Africa. It is still currently under active development
View Project >This application connects students and instructions by making students to subscribe to a course created by an instructor. By so doing, students can interact with each other and also ask valuable question from instructor
View Project >This was a project built for a client. The aim of the project is for users to have access to realtime predictions of football scores
View Project >The main aim of this project is to minimize and eventually stop the waste of books in the University of Ibadan . We give book owner the platform to upload "No Longer Useful books to me" either softcopy or hardcopy. We make pdf's downloadable to anyone irrespective of their race or culture and we connect those that upload hard copy books(in form of an image with some descriptions) to those that needs it through SMS(text messages).
View Project >


This page was generated by JCAlgTest tool
Execution date/time: 2015/07/23 14:56:52, CSV source data
AlgTestJClient version: 1.6.0
AlgTest applet version: 1.6.0
Used reader: PC/SC terminal Gemplus USB Smart Card Reader 2
Card ATR: 3b f8 13 00 00 81 31 fe 45 4a 43 4f 50 76 32 34 31 b7
JavaCard version: 2.2
MEMORY_TYPE_PERSISTENT: -1B
MEMORY_TYPE_TRANSIENT_RESET: -1B
MEMORY_TYPE_TRANSIENT_DESELECT: -1B
If you will spot any discrepancies in the presented data (e.g. strange error, too fast or too slow operation time etc.), please open an issue (click at New issue) at GitHub. Thank you!
You can find information about testing on GitHub wiki.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.
GRAPH IS LOADING. THIS MAY TAKE 5.30 SECONDS DEPENDING ON THE NUMBER OF GRAPHS.


Capture and Share
the World's Moments
Instagram is a fast, beautifu and fun way to share your life with friends and family.
Take a picture or video, choose a filter to transform its look and feel, then post to Instagram — it's that easy. You can even share to Facebook, Twitter, Tumblr and more. It's a new way to see the world.
Oh yeah, did we mention it's free?


Welcome to FileFish
please select where you would like to be directed
Search for System
Add Data to Existing System
Enter a new System


Fredericton Marathon
Fredericton NB/CAN
Website: frederictonmarathon.ca
Race Winners
(39 runnings)
3:00:18 3:11:43 3:16:04 3:17:38 3:06:31 13 May
2007
2:46:47
3:23:06
14 May
2006
2:55:14*
3:30:15
08 May
2005
2:41:40
3:36:07
09 May
2004
2:45:40
3:30:43
04 May
2003
2:48:12.6
3:31:02.0
05 May
2002
2:51:59
3:28:32
06 May
2001
3:03:26
3:43:40
07 May
2000
3:09:00
3:25:35
02 May
1999
3:10:45
3:21:36
03 May
1998
3:09:55
3:21:58
04 May 1997
---
3:21:41
1996
---
---
07 May
1995
2:42:
3:20:55
1994
---
---
02 May
1993
3:09:10
3:45:17
03 May
1992
2:54:02
3:29:38
05 May
1991
2:43:53
3:50:52
05 May
1990
2:54:19
3:50:47
06 May
1989
2:36:15
---
1988
---
---
1987
---
---
1986
---
---
14 Apr
1985
---
---
08 Apr
1984
2:42:13 3:50:08 10 Apr
1983
2:27:21
3:41:01
11 Apr
1982
---
---
19 Apr
1981
2:51:44
3:44:21
06 Apr
1980
2:44:02 3:50: 15 Apr
1979
2:49:45
4:15:40
Notes: 1979 is believed to have been the inaugural year. This race was known as the New Brunswick Heart Marathon
for 1989-1993. In 2006, Chris Brake was first across the finish line but was disqualified for being helped before
he was able to finish.
14 May
2017
2:37:59
Ryan O'Shea-2
3:03:39
Heather O'Donnell (NS/CAN)
08 May
2016
2:39:23
Ryan O'Shea (NB/CAN)
3:07:49
Maura Wieczorek (NS/CAN)
10 May
2015
2:47:31
David MacLennan (NS/CAN)
3:04:04
Chantelle Grenier (PQ/CAN)
11 May
2014
2:44:40
Chuck Dixon-3
2:53:57
Paula Keating (NB/CAN)
12 May
2013
2:45:33
Chuck Dixon-2
3:12:46
Cathy Jeffrey (NB/CAN)
13 May
2012
2:42:10
Chuck Dixon (NB/CAN)
Rayleen Hill (NS/CAN)
08 May
2011
2:35:42
Chris Brake-8
Susan Carbyn (NS/CAN)
09 May
2010
2:34:47
Chris Brake-7
Margaret
Johnson-3
10 May
2009
2:47:34
Alex Coffin (NB/CAN)
Hazel Caldwell (CAN)
11 May
2008
2:43:36
Travis Saunders (ON/CAN)
Janice Ashworth (NS/CAN)
Chris Brake-6
Margaret Johnson-2
Len Falkenstein (NB/CAN)
Margaret Johnson (NB/CAN)
Chris Brake-5
Tara Larkin (PE/CAN)
Chris Brake-4
Pam Power-4
Chris Brake-3
Tricia Groundwater (NB/CAN)
Chris Brake-2
Bronwyn Tanner (CAN)
Chris Brake (NB/CAN)
Jennifer Hoyt (NS/CAN)
Francis Fagan-3
Pam Power-3
Francis Fagan-2
Kathy Wilson (CAN)
Francis Fagan (CAN)
Pam Power-2
n/a
Pam Power (PE/CAN)
n/a
n/a
Paul Morrison (NB/CAN)
Paula MacInnis (NB/CAN)
n/a
n/a
Bob Unger (NB/CAN)
Simone Boudreau (NB/CAN)
Noel Gallant-2
Coralie English (NB/CAN)
Noel Gallant (NB/CAN)
Jennifer Alexia Stewart (NB/CAN)
Derek Fisher (CAN)
Sharon Modorski (IL/USA)
Scott Hare (NB/CAN)
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
Gary Cochrane (CAN)
Lisa Frink (CAN)
Patrick Montuoro (CAN)
Denyse Pelletier (CAN)
n/a
n/a
Phil Meagher (CAN)
R Wagener (CAN)
Joe McGuire (CAN)
Francie Dunn (CAN)
Leo Glavine (CAN)
Lauretta Harris (CAN)
Most Wins
(1979/date)
Men
8
Chris Brake (NB/CAN)
2001-05,2007,2010-11
Women
4
Pam Power (PE/CAN)
1997-98,2000,2004
Prize Money
(ADR qualified runners)
Year Men Women Total
2014 none $230 $230
....
2012 none 250 250
Sums $0 $480 $480
Note: Prize money only for event records.
Race Time Bias
(sec/km)
Insufficient data to calculate the race time bias.
Competitive Level
(1990-date)
Insufficient data to calculate the competitive level.
Quality Performances
Men No men under 2:20 Women No women under 2:50
Last Updated on 15 May 2017
Contributors: Juraj Gasparovic (4), Maurice Wilson (27)


Page maintained by Ke-Sen Huang and Tim Rowley.
Tim has a mirror page here. If you have additions or changes, send an e-mail.
Information here is provided with the permission of the ACM.
Note that when possible I link to the page containing the link to the actual PDF or PS of the preprint.
I prefer this as it gives some context to the paper and avoids possible copyright problems with direct linking.
Thus you may need to search on the page to find the actual document.
ACM Digital Library: ACM Transactions on Graphics (TOG) Volume 24 , Issue 3 (July 2005) Proceedings of ACM SIGGRAPH 2005
the ACM Digital Library (DOI) Link for the paper
the link of author version paper
the link of project page
Changelog
Skin & Faces
- Skinning Mesh Animations
-
Doug L. James,
Christopher D. Twigg
(Carnegie Mellon University)
- SCAPE: Shape Completion and Animation of People
-
Drago Anguelov,
Praveen Srinivasan,
Daphne Koller,
Sebastian Thrun,
J. Rodgers (Stanford University),
James Davis (University of California, Santa Cruz)
- Automatic Determination of Facial Muscle Activations From Sparse Motion Capture Marker Data
-
Eftychios Sifakis,
Igor Neverov (Stanford University),
Ron Fedkiw
(Stanford University and Industrial Light & Magic)
- Face Transfer With Multilinear Models
-
Daniel Vlasic (Massachusetts Institute of Technology),
Matt Brand,
Hanspeter Pfister (Mitsubishi Electric Research Laboratories),
Jovan Popovic
(Massachusetts Institute of Technology)
Hardware Rendering
- RPU: A Programmable Ray Processing Unit for Realtime Ray Tracing
-
Sven Woop,
Jorg Schmittler,
Philipp Slusallek
(Universität des Saarlandes)
- User-Configurable Automatic Shader Simplification
-
Fabio Pellacini
(Cornell University)
- A Relational Debugging Engine for the Graphics Pipeline
-
Nathaniel Duca,
Krzysztof Niski,
Jonathan Bilodeau,
Matthew Bolitho,
Yuan Chen,
Jonathan Cohen,
(John Hopkins University)
- Lpics: A Hardware-Accelerated Relighting Engine for Computer Cinematography
-
Fabio Pellacini,
Kiril Vidimce,
Aaron Lefohn,
Alex Mohr,
Mark Leone,
John Warren
(Pixar Animation Studios)
Mesh Manipulation
- Meshless Deformations Based on Shape Matching
-
Matthias Müller,
Bruno Heidelberger
(Eidgenössische Technische Hochschule Zürich ),
Matthias Teschner
(Universität Freiburg),
Markus Gross
(Eidgenössische Technische Hochschule Zürich )
- Linear Rotation-Invariant Coordinates for Meshes
-
Yaron Lipman,
Olga Sorkine,
David Levin,
Daniel Cohen-Or
(Tel Aviv University)
- Mesh-based Inverse Kinematics
-
Robert W. Sumner,
Matthias Zwicker (Massachusetts Institute of Technology),
Craig Gotsman
(Harvard University),
Jovan Popovic
(Massachusetts Institute of Technology)
- Large Mesh Deformation Using the Volumetric Graph Laplacian
-
Kun Zhou (Microsoft Research Asia),
Jin Huang (Zhejiang University),
John Snyder (Microsoft Research),
Xinguo Liu (Microsoft Research Asia),
Hujun Bao (Zhejiang University),
Baining Guo,
Heung-Yeung Shum
(Microsoft Research Asia)
Illustration and Image-Based Modeling
- MoXi: Real-Time Ink Dispersion in Absorbent Paper
-
Nelson S.-H. Chu,
Chiew-Lan Tai
(Hong Kong University of Science and Technology)
- Line Drawings From Volume Data
-
Michael Burns,
Janek Klawe,
Szymon Rusinkiewicz,
Adam Finkelstein
(Princeton University),
Doug DeCarlo
(Rutgers University)
- Motion magnification
-
Ce Liu,
Antonio Torralba,
William T. Freeman,
Frédo Durand,
Edward H. Adelson
(Massachusetts Institute of Technology)
- Out-of-Core Tensor Approximation of High Dimensional Visual Data
-
Hongcheng Wang,
Qing Wu,
Lin Shi,
Yizhou Yu,
Narendra Ahuja
(University of Illinois Urbana-Champaign)
Meshes I
- Efficiently Combining Positions and Normals for Precise 3D Geometry
-
Diego Nehab,
Szymon Rusinkiewicz
(Princeton University),
James Davis
(University of California, Santa Cruz),
Ravi Ramamoorthi
(Columbia University)
- Robust Moving Least-squares Fitting with Sharp Features
-
Shachar Fleishman,
(University of Utah),
Daniel Cohen-Or
(Tel Aviv University),
Claudio Silva
(University of Utah)
- Fast Exact and Approximate Geodesics on Meshes
-
Vitaly Surazhsky,
Tatiana Surazhsky
(University of Oslo and Technion),
Danil Kirsanov,
Steven J. Gortler
(Harvard University),
Hugues Hoppe
(Microsoft Research)
- Mean Value Coordinates for Closed Triangular Meshes
-
Tao Ju,
Scott Schaefer,
Joe Warren
(Rice University)
Video & Image Matting
- Defocus Video Matting
-
Morgan McGuire,
Wojciech Matusik,
Hanspeter Pfister
(Mitsubishi Electric Research Laboratories (MERL)),
John F. Hughes
(Brown University),
Frédo Durand
(Massachusetts Institute of Technology)
- Automatic Photo Pop-upProject
-
Derek Hoiem,
Alexei Efros,
Martial Hebert
(Carnegie Mellon University)
- Interactive Video Cutout
-
Jue Wang,
Pravin Bhat
(University of Washington),
Alex Colburn,
Maneesh Agrawala,
Michael Cohen
(Microsoft Research)
- Video Object Cut and Paste
-
Yin Li,
Jian Sun,
Heung-Yeung Shum
(Microsoft Research Asia)
Meshes II
- Surface Compression With Geometrical Bandelets
-
Gabriel Peyré,
Stéphane Mallat
(CMAP Ecole Polytechnique)
- Geometry-guided Progressive Lossless 3D Mesh Coding with Octree (OT) Decomposition
-
Jingliang Peng,
C.-C. Jay Kuo
(University of Southern California)
- Variational Tetrahedral Meshing
-
Pierre Alliez,
David Cohen-Steiner,
Mariette Yvinec
(INRIA),
Mathieu Desbrun
(Caltech)
- Shell Maps
-
Serban D. Porumbescu,
Brian Budge,
Louis Feng,
Kenneth I. Joy
(University of California Davis)
Perception
- Color2Gray: Salience-Preserving Color Removal
-
Amy A. Gooch,
Sven C. Olsen,
Jack Tumblin,
Bruce Gooch
(Northwestern University)
- Evaluation of Tone Mapping Operators using a High Dynamic Range Display
-
Ledda Patrick,
Alan Chalmers,
Tom Troscianko
(University of Bristol),
Helge Seetzen
(Sunnybrook Technologies)
- A Photon Accurate Model of the Human Eye
-
Michael F. Deering
- Mesh Saliency
-
Chang Ha Lee,
Amitabh Varshney,
David W. Jacobs
(University of Maryland at College Park)
Motion Capture Data: Interaction and Selection
- Action Synopsis: Pose Selection and Illustration
-
Jackie Assa,
Yaron Caspi,
Daniel Cohen-Or
(Tel Aviv University)
- Efficient Content-Based Retrieval of Motion Capture Data
-
Meinard Mueller,
Tido Roeder,
Michael Clausen
(Universität Bonn)
- Performance Animation From Low-dimensional Control Signals
-
Jinxiang Chai,
Jessica K. Hodgins
(Carnegie Mellon University)
- Dynamic Response for Motion Capture Animation
-
Victor Zordan,
Bill Chiu,
Anna Majkowska,
Matthew Fast
( University of California, Riverside)
Plants
- Modeling and Visualization of Leaf Venation Patterns
-
Adam Runions,
Martin Fuhrer,
Brendan Lane,
Pavol Federl,
Anne-Gaëlle Rolland-Lagan,
Przemyslaw Prusinkiewicz
(University of Calgary)
- Real-Time Rendering of Plant Leaves
-
Lifeng Wang
(Microsoft Research Asia),
Wenle Wang
(Tsinghua University),
Julie Dorsey
(Yale University),
Xu Yang (Nankai University),
Baining Guo,
Heung-Yeung Shum
(Microsoft Research Asia)
- Floral Diagrams and Inflorescences: Interactive Flower Modeling Using Botanical Structural Constraints
-
Takashi Ijiri
(The University of Tokyo),
Shigeru Owada
(The University of Tokyo and Sony CSL),
Makoto Okabe,
(The University of Tokyo),
Takeo Igarashi
(The University of Tokyo and JST/PRESTO)
- Measuring and Modeling the Appearance of Wood
-
Steve R. Marschner,
Stephen H. Westin,
Adam Arbree,
Jonathan T. Moon
(Cornell University)
Capturing Reality I
- Fourier Slice Photography
-
Ren Ng
(Stanford University)
- Dual Photography
-
Pradeep Sen,
Billy Chen,
Gaurav Garg
(Stanford University),
Steve Marschner
(Cornell University),
Mark Horowitz,
Marc Levoy,
Hendrik P. A. Lensch
(Stanford University)
- Performance relighting and reflectance transformation with time-multiplexed illumination
-
Andreas Wenger,
Andrew Gardner,
Chris Tchou,
Jonas Unger,
Tim Hawkins,
Paul Debevec
(University of Southern California, Institute for Creative Technologies)
- High Performance Imaging Using Large Camera Arrays
-
Bennett Wilburn
(Stanford University),
Neel Joshi
(University of California, San Diego),
Vaibhav Vaish,
Eino-Ville Talvala,
Emilio Antunez,
Adam Barth,
Andrew Adams,
Mark Horowitz,
Marc Levoy
(Stanford University)
Texture Synthesis
- Parallel Controllable Texture Synthesis
-
Sylvain Lefebvre,
Hugues Hoppe
(Microsoft Research)
- Texture design using a simplicial complex of morphable textures
-
Wojciech Matusik
(Mitsubishi Electric Research Laboratories (MERL)),
Matthias Zwicker,
Frédo Durand
(Massachusetts Institute of Technology)
- Texture Optimization for Example-based Synthesis
-
Vivek Kwatra,
Irfan Essa,
Aaron F. Bobick,
Nipun Kwatra
(Georgia Institute of Technology)
- Wavelet Noise
-
Rob Cook,
Tony DeRose
(Pixar Animation Studios)
Capturing Reality II
- Acqusition of Time-Varying Participating Media
-
Tim Hawkins,
Per Einarsson,
Paul Debevec
(University of Southern California, Institute for Creative Technologies)
- Modeling Hair From Multiple Views
-
Yichen Wei
(Hong Kong University of Science and Technology),
Eyal Ofek
(Microsoft Research Asia),
Long Quan
(Hong Kong University of Science and Technology),
Heung-Yeung Shum
(Microsoft Research Asia)
- Panoramic video textures
-
Aseem Agarwala,
Colin Zheng
(University of Washington),
Chris Pal
(University of Massachusetts Amherst),
Maneesh Agrawala,
Michael F. Cohen
(Microsoft Research),
Brian Curless,
(University of Washington),
David Salesin
(University of Washington and
Microsoft Research),
Richard Szeliski
(Microsoft Research)
- Removing Photography Artifacts Using Gradient Projection and Flash-Exposure Sampling
-
Amit Agrawal,
Ramesh Raskar
(Mitsubishi Electric Research Laboratories (MERL)),
Shree K. Nayar
(Columbia University)
Yuanzhen Li,
(Massachusetts Institute of Technology)
Image Processing
- Compressing and Companding High Dynamic Range Images with Subband Architectures
-
Yuanzhen Li,
Lavanya Sharan,
Edward H. Adelson,
(Massachusetts Institute of Technology)
- Video Enhancement Using Per-Pixel Virtual Exposures
-
Eric P. Bennett,
Leonard McMillan
(University of North Carolina at Chapel Hill)
- Animating Pictures with Stochastic Motion Textures
-
Yung-Yu Chuang
(National Taiwan University),
Dan B. Goldman,
Colin Zheng,
Brian Curless,
(University of Washington)
David Salesin
(University of Washington and
Microsoft Research),
Richard Szeliski
(University of Washington)
- Image Completion with Structure Propagation
-
Jian Sun
(Microsoft Research Asia),
Lu Yuan
(Tsinghua University),
Jiaya Jia
(Chinese University of Hong Kong),
Heung-Yeung Shum
(Microsoft Research Asia)
Large Models & Large Displays
- GoLD: Interactive Display of Huge Colored and Textured Models
-
Louis Borgeat,
Guy Godin,
Philippe Massicotte,
Français Blais (National Research Council of Canada),
Christian Lahanier
(Centre de Recherche et de Restauration des Musées de France)
- Far Voxels: A Multiresolution Framework for Interactive Rendering of Huge Complex 3D Models on Commodity Graphics Platforms
-
Enrico Gobbetti,
Fabio Marton
(Center for Advanced Studies, Research and Development in Sardinia)
- Cache-Oblivious Mesh Layouts
-
Sung-Eui Yoon (University of North Carolina at Chapel Hill),
Peter Lindstrom,
Valerio Pascucci
(Lawrence Livermore National Laboratory),
Dinesh Manocha
(University of North Carolina at Chapel Hill)
- The Varrier Autostereoscopic Virtual Reality Display
-
Daniel J. Sandin,
Todd Margolis,
Jinghua Ge,
Javier Girado,
Tom Peterka,
Thomas A. DeFanti
(University of Illinois at Chicago, Electronic Visualization Laboratory)
Fluid Simulation
- Animating Gases with Hybrid Meshes
-
Bryan Feldman,
James F. O'Brien,
Bryan M. Klingner
(University of California, Berkeley)
- A Vortex Particle Method for Smoke, Fire, and Explosions
-
Andrew Selle
(Stanford University and
Intel Corporation),
Nick Rasmussen (Industrial Light & Magic),
Ron Fedkiw
(Stanford University and Industrial Light & Magic)
- Discontinuous Fluids
-
Jeong-Mo Hong,
Chang-Hun Kim
(Korea University)
- Water Drops on Surfaces
-
Huamin Wang,
Peter J. Mucha,
Greg Turk
(Georgia Institute of Technology)
Reprise of UIST and I3D
The User-Interface Software and Technology Symposium and the Symposium on Interactive 3D Graphics and Games are two leading conferences sponsored by ACM SIGGRAPH. Five of the best papers from the most recent UIST and I3D symposia are presented in abbreviated form.
Dynamics of Solids
- Adaptive Dynamics of Articulated Bodies
-
Stephane Redon,
Nico Galoppo,
Ming C. Lin
(University of North Carolina)
- Fast Frictional Dynamics for Rigid Bodies
-
Danny Kaufman,
Timothy Edmunds,
Dinesh K. Pai
(Rutgers University)
- Meshless Animation of Fracturing Solids
-
Mark Pauly
(Stanford University),
Richard Keiser
(Eidgenössische Technische Hochschule Zürich ),
Bart Adams,
Philip Dutré
(Katholieke Universiteit Leuven),
Markus Gross
(Eidgenössische Technische Hochschule Zürich),
Leonidas Guibas
(Stanford University)
Deformable Models
- Animating Sand as a Fluid
-
Yongning Zhu,
Robert Bridson,
(University of British Columbia)
- Coupling Water and Smoke to Thin Deformable and Rigid Shells
-
Eran Guendelman
(Stanford University and Industrial Light & Magic)
Andrew Selle
(Stanford University and
Intel Corporation),
Frank Losasso,
Ronald Fedkiw
(Stanford University and Industrial Light & Magic)
- Real-Time Subspace Integration for St.Venant-Kirchhoff Deformable Models
-
Jernej Barbic,
Doug L. James
(Carnegie Mellon University)
- Interactive Collision Detection Between Deformable Models Using Chromatic Decomposition
-
Naga Govindaraju,
David Knott,
Nitin Jain,
Ilknur Kabul
(University of North Carolina at Chapel Hill),
Rasmus Tamstorf
(Walt Disney Feature Animation),
Russel Gayle,
Ming C. Lin,
Dinesh Manocha
(University of North Carolina at Chapel Hill)
Geometry on GPUs
- Resolution Independent Curve Rendering Using Programmable Graphics Hardware
-
Charles Loop,
Jim Blinn
(Microsoft Research)
- A Realtime GPU Subdivision Kernel
-
Le-Jeng Shiue,
Ian Jones,
Jorg Peters
(University of Florida)
- GPU-Based Trimming and Tessellation of NURBS and T-Spline Surfaces
-
Michael Guthe,
Ákos Balázs,
Reinhard Klein
(Universität Bonn)
- Blister: GPU-based rendering of Boolean combinations of free-form triangulated shapes
-
John Hable,
Jarek Rossignac
(Georgia Institute of Technology)
Transparency & Translucency
- Light Diffusion in Multi-Layered Translucent Materials
-
Craig Donner,
Henrik Wann Jensen
(University of California at San Diego)
- A Practical Analytic Single Scattering Model for Real Time Rendering
-
Bo Sun,
Ravi Ramamoorthi
(Columbia University),
Srinivasa Narasimhan
(Carnegie Mellon University),
Shree Nayar
(Columbia University)
- An Approximate Image-Space Approach for Interactive Refraction
-
Chris Wyman
(University of Iowa)
- Modeling and Rendering of Quasi-Homogeneous Materials
-
Xin Tong
(Microsoft Research Asia),
Jiaping Wang
(Institute of Computing Technology, Chinese Academy of Sciences),
Steve Lin,
Baining Guo,
Heung-Yeung Shum
(Microsoft Research Asia)
Styles of Human Motion
- Geostatistical Motion Interpolation
-
Tomohiko Mukai,
Shigeru Kuriyama
(Toyohashi University of Technology)
- Learning Physics-Based Motion Style With Nonlinear Inverse Optimization
-
C. Karen Liu
(University of Washington),
Aaron Hertzmann
(University of Toronto),
Zoran Popovic
(University of Washington)
- Style Translation for Human Motion
-
Eugene Hsu
(Massachusetts Institute of Technology),
Kari Pulli
(Nokia / Massachusetts Institute of Technology),
Jovan Popovic
(Massachusetts Institute of Technology)
- A Data-Driven Approach to Quantifying Natural Human Motion
-
Liu Ren
(Carnegie Mellon University),
Alton Patrick
(Georgia Institute of Technology),
Alexei Efros,
Jessica K. Hodgins
(Carnegie Mellon University),
James Rehg
(Georgia Institute of Technology)
Appearance & Illumination
- Lightcuts: A Scalable Approach to Illumination
-
Bruce Walter,
Sebastian Fernandez,
Adam Arbree,
Kavita Bala,
Michael Donikian,
Donald P. Greenberg
(Cornell University)
- Fast and Detailed Approximate Global Illumination by Irradiance Decomposition
-
Okan Arikan,
David Forsyth,
James F. O'Brien
(University of California at Berkeley)
- A Frequency Analysis of Light Transport
-
Frédo Durand
(Massachusetts Institute of Technology),
Nicolas Holzschuch,
Cyril Soler
(ARTIS, GRAVIR/IMAG -- INRIA),
Eric Chan
(Massachusetts Institute of Technology),
Français X. Sillion
(ARTIS, GRAVIR/IMAG -- INRIA)
- Visual Simulation of Weathering by gamma-ton Tracing
-
Yanyun Chen
(Microsoft Research Asia),
Lin Xia (Zhejiang University),
Tien Tsin Wong
(Chinese University of Hong Kong),
Xin Tong,
Hujun Bao
(Zhejiang University),
Baining Guo,
Heung-Yeung Shum
(Microsoft Research Asia)
Shape & Texture
- As-Rigid-As-Possible Shape Manipulation
-
Takeo Igarashi (University of Tokyo),
Tomer Moscovich,
John F. Hughes
(Brown University)
- A Sketch-Based Interface for Detail-Preserving Mesh Editing
-
Andy Nealen
(Technische Universität Darmstadt),
Olga Sorkine
(Tel Aviv University),
Marc Alexa
(Technische Universität Darmstadt),
Daniel Cohen-Or
(Tel Aviv University)
- TextureMontage:Seamless Texturing of Arbitrary Surfaces From Multiple Images
-
Kun Zhou,
Xi Wang
(Microsoft Research Asia),
Yiying Tong,
Mathieu Desbrun
(Caltech),
Baining Guo,
Heung-Yeung Shum
(Microsoft Research Asia)
Ray Tracing
- Soft Shadow Volumes for Ray Tracing
-
Samuli Laine
(Helsinki University of Technology),
Timo Aila,
(Helsinki University of Technology and
Hybrid Graphics, Ltd.),
Ulf Assarsson
(ARTIS, GRAVIR/IMAG -- INRIA and
Illuminate Labs, Ltd.),
Jaakko Lehtinen
(Helsinki University of Technology and
Remedy Entertainment, Ltd.),
Tomas Akenine-Möller
(Lunds universitet)
- Wavelet Importance Sampling: Efficiently Evaluating Products of Complex Functions
-
Petrik Clarberg
( Lunds universitet),
Wojciech Jarosz
(University of California, San Diego),
Tomas Akenine-Möller
(Lunds universitet),
Henrik Wann Jensen
(University of California, San Diego)
- Multi-Level Ray Tracing Algorithm
-
Alexander Reshetov,
Alexei Soupikov,
Jim Hurley
(Intel Corporation)
- Energy redistribution path tracing
-
David Cline,
Justin Talbot,
Parris Egbert
(Brigham Young University)
Precomputed Light Transport
- Precomputed Shadow Fields for Dynamic Scenes
-
Kun Zhou,
Yaohua Hu,
Steve Lin,
Baining Guo,
Heung-Yeung Shum
(Microsoft Research Asia)
- All-frequency Interactive Relighting of Translucent Objects with Single and Multiple Scattering
-
Rui Wang,
John Tran,
David Luebke
(University of Virginia)
- Precomputed Local Radiance Transfer for Real-Time Lighting Design
-
Anders Wang Kristensen
(University of California, San Diego),
Tomas Akenine-Möller
(Lunds universitet),
Henrik Wann Jensen
(University of California, San Diego)
- Local, Deformable Precomputed Radiance Transfer
-
Peter-Pike Sloan,
Ben Luna,
(Microsoft Corporation),
John Snyder
(Microsoft Research)
<EMAIL_ADDRESS>kesen.huang@gmail.com


Preparation time
overnight
Cooking time
1 to 2 hours
Serves
Serves 4
A gorgeous casserole for a hearty winter supper. Great served with mashed potatoes and a crisp salad.
Place all the marinade ingredients in a bowl, add the turkey pieces and leave to marinade for at least six hours or, preferably, overnight.
Heat a large pan or flameproof casserole and add a knob of butter. Add the pancetta and lightly brown then remove it from the pan and set aside. In the same pan, cook the mushrooms and onions for a few minutes until they colour then remove them from the pan and set the pan aside.
Remove the turkey from the marinade, strain the liquid over a bowl and discard the vegetables. Dip the turkey into the seasoned flour, shaking off the excess. Return the pan to the hob on a high heat and brown the turkey pieces on all sides. Turn down the heat and add the mushrooms, onions, carrot and celery along with the thyme and bay leaf. Pour in the strained marinade and simmer for one hour. Let the casserole rest for about 15 minutes then add the parsley and serve.


The parties consent to the maintenance of this agreement via electronic methods. The parties to this agreement agree that the provision of electronic signatures shall be considered necessary and sufficient proof of their intent to contract as defined by the laws governing this agreement. The parties acknowledge that some of the evidence, and deliverables which are integral to the successful fulfillment of this agreement shall be tracked within an electronic network known as a "blockchain" at the uniquely identifiable address below


This part seems harder to find than the others. These are some of the possible alternatives: - MAX6010AEUR - MAX6063AEUR - ISL21010CFH330Z - MAX6035AAUR30 may work, not personally tested. - LM4120AIM5-3.0 may work, not personally tested.


Attention: Friend, I am Barrister Vincent Usman a Solicitor. I am the Personal Attorney to Mr. John Anderson a foreigner, who was a contractor to Shell Petroleum Development Company in Nigeria(SPDC). On the 26th of September 1992, my client, his wife and their three children were involved in a Plane crash on their way to Yankari Games Reserve for 2week`s holiday. Unfortunately they all lost their lives in the plane crash, Since then I have made several enquiries to his Embassy and the home address he filled in his file in my office to locate any of his extended relatives, this has also proved unsuccessful. After these several unsuccessful attempts, I decided to use the Internet to locate any member of his family but to no avail, hence I contacted you. I contacted you to assist in repatriating the money and property left behind by my client before they get confiscated or declared unserviceable by the SECURITY & FINANCE HOUSE where this fund is deposited. Particularly, the FINANCE HOUSE where the deceased had an account valued at about US$9M (Nine million dollars). Conseqently, the bank issued me a notice to provide the next of kin or have the account confiscated. since I have been unsuccessful in locating the relatives for over 10 years now. I seek your consent to present you as the next of kin of the deceased since you are a foreigner so that the proceeds of this account valued at US$9M can be paid to you and I. We shall share the money thus 55% to me and 40% to you, while 5% will be used to re-imburse any expenses that might be incurred on both ends and to service the tax that might incur be in your country. I have all the necessary legal documents that can be used to back up any claim we may make. All I require is your honest cooperation to enable us seeing this deal through. I guarantee that this will be executed under a legitimate arrangement that will protect you from any breach of the law. Yours Faithfully, Barrister Vincent Usman(Esq). N.B. Please indicate your telephone and fax numbers for easy communication in this mutual transaction. ---------------------------------------------------------------- Ce service de mailing vous est offert par http://www.freesurf.fr. FreeSurf, votre acces ADSL a partir de 29 euros/mois http://www.freesurf.fr/adsl/


I am a responsive designer who thrives on user experience. When I'm not working, pursing side projects, or getting lost in a book I can be found working on my photography or spending time with my family. That includes my husband, baby, dog and cat!
I was born and raised in south Florida, but my family heritage lies in southern Italy. I have family in Sicily that I keep in touch with. As a first generation american, I have family in Sicily that I've had to visit often. As a result is that I now hate traveling.
My passion: I LOVE art - its been one of the most influential and guiding forces in my life. I think art has the power to make a positive difference in the world by introducing new ways of thinking and looking at things. I get my fix by visiting galleries and museums.
A fun fact: I love learning and trying new things, and as a native Floridian I love outdoor activities! I'm a beginner roller skater, and recently sprained my ankle while teaching myself how to skate! I can't wait to get back on my skates and roll!


Free PBR Textures - ShareTextures
by Share TexturesShareTextures writes:
We have 500+ PBR textures up to 4K resolution in our archives. You can access them using sharetextures.com.
If you want to download all of them using google-drive consider become a patron and support us.
We can grove more with your support. Also based on your patron tier, you can access patron-exclusive textures, real textures sets and more. For more information check our patreon page.
I want to thanks Blendernation team for their support to sharetextures.com!
Here are some of the textures:


MapSwipe Workers - Command Line Interface¶
Usage: mapswipe_workers [OPTIONS] COMMAND [ARGS]...
Options:
-v, --verbose
--version Show the version and exit.
--help Show this message and exit.
Commands:
create-projects
firebase-to-postgres
generate-stats
run
Create projects from submitted project drafts¶
Usage: mapswipe_workers create-projects [OPTIONS]
Options:
-s, --schedule [m|h|d] Will create projects every 10 minutes (m), every
hour (h) or every day (d).
--help Show this message and exit.
Transfer data from Firebase to Postgres¶
Usage: mapswipe_workers firebase-to-postgres [OPTIONS]
Options:
-s, --schedule [m|h|d] Will update and transfer relevant data (i.a. users
and results) from Firebase into Postgres every 10
minutes (m), every hour (h) or every day (d).
--help Show this message and exit.
Generate Statistics¶
Usage: mapswipe_workers generate-stats [OPTIONS]
Options:
-s, --schedule [m|h|d] Will generate stats every 10 minutes (m), every hour
(h) or every day (d).
--help Show this message and exit.


Starting with a clean slate
With a new blog comes new responsiblity.
So here we are. This should be interesting. I’ve finally gotten round to getting this website into a state in which I feel happy enough to start publishing artciles. On top of that I have now made the efford to find time and actually write stuff, which is good. Well it’s good for me anyway.
Now with that said, what is it that you can expect from me and this website? My plan is to write about anything and everything that I want to have a discusion about. I’m a Designer and Illustrator by trade so expect articles relate to those fields to pop up a lot. But also on top of that I’d like this to be a place where I can speak my mind about whatever currently sparks my interest. Weither thats a cool new place I’ve found, upcoming travel plans, bullshit my friends are going on about, general day to day troubles, the lot.
So If I’ve sparked your interest then welcome! And I look forward to chating with you soon. To everyone else, thanks for dropping by and hopefully we will meet again some time in the future :)


A B C D E F G I K M N O P S T U
| as.list-method | TxDb objects |
| asBED-method | Coerce to file format structures |
| asGFF-method | Coerce to file format structures |
| browseUCSCtrack | Make a TxDb object from annotations available at the UCSC Genome Browser |
| cds | Extract genomic features from a TxDb-like object |
| cds-method | Extract genomic features from a TxDb-like object |
| cdsBy | Extract and group genomic features of a given type from a TxDb-like object |
| cdsBy-method | Extract and group genomic features of a given type from a TxDb-like object |
| cdsByOverlaps | Extract genomic features from a TxDb-like object based on their genomic location |
| cdsByOverlaps-method | Extract genomic features from a TxDb-like object based on their genomic location |
| class:FeatureDb | FeatureDb objects |
| class:TxDb | TxDb objects |
| columns-method | Using the "select" interface on TxDb objects |
| coordinate-mapping | Map range coordinates between transcripts and genome space |
| coverageByTranscript | Compute coverage by transcript (or CDS) of a set of ranges |
| DEFAULT_CIRC_SEQS | character vector: strings that are usually circular chromosomes |
| disjointExons | Extract non-overlapping exon parts from an object |
| disjointExons-method | Extract non-overlapping exon parts from an object |
| distance-method | Finding the nearest genomic range neighbor in a TxDb |
| exonicParts | Extract non-overlapping exonic or intronic parts from a TxDb-like object |
| exons | Extract genomic features from a TxDb-like object |
| exons-method | Extract genomic features from a TxDb-like object |
| exonsBy | Extract and group genomic features of a given type from a TxDb-like object |
| exonsBy-method | Extract and group genomic features of a given type from a TxDb-like object |
| exonsByOverlaps | Extract genomic features from a TxDb-like object based on their genomic location |
| exonsByOverlaps-method | Extract genomic features from a TxDb-like object based on their genomic location |
| extractTranscriptSeqs | Extract transcript (or CDS) sequences from chromosome sequences |
| extractTranscriptSeqs-method | Extract transcript (or CDS) sequences from chromosome sequences |
| extractUpstreamSeqs | Extract sequences upstream of a set of genes or transcripts |
| extractUpstreamSeqs-method | Extract sequences upstream of a set of genes or transcripts |
| FeatureDb | FeatureDb objects |
| FeatureDb-class | FeatureDb objects |
| features | Extract simple features from a FeatureDb object |
| features-method | Extract simple features from a FeatureDb object |
| fiveUTRsByTranscript | Extract and group genomic features of a given type from a TxDb-like object |
| fiveUTRsByTranscript-method | Extract and group genomic features of a given type from a TxDb-like object |
| genes | Extract genomic features from a TxDb-like object |
| genes-method | Extract genomic features from a TxDb-like object |
| getChromInfoFromBiomart | Make a TxDb object from annotations available on a BioMart database |
| getChromInfoFromUCSC | Make a TxDb object from annotations available at the UCSC Genome Browser |
| getPromoterSeq | Get gene promoter sequences |
| getPromoterSeq-method | Get gene promoter sequences |
| id2name | Map internal ids to external names for a given feature type |
| intronicParts | Extract non-overlapping exonic or intronic parts from a TxDb-like object |
| intronsByTranscript | Extract and group genomic features of a given type from a TxDb-like object |
| intronsByTranscript-method | Extract and group genomic features of a given type from a TxDb-like object |
| isActiveSeq | TxDb objects |
| isActiveSeq-method | TxDb objects |
| isActiveSeq<- | TxDb objects |
| isActiveSeq<--method | TxDb objects |
| keys-method | Using the "select" interface on TxDb objects |
| keytypes-method | Using the "select" interface on TxDb objects |
| makeFDbPackageFromUCSC | Making a TxDb package from annotations available at the UCSC Genome Browser, biomaRt or from another source. |
| makeFeatureDbFromUCSC | Making a FeatureDb object from annotations available at the UCSC Genome Browser |
| makePackageName | Making a TxDb package from annotations available at the UCSC Genome Browser, biomaRt or from another source. |
| makeTxDb | Making a TxDb object from user supplied annotations |
| makeTxDbFromBiomart | Make a TxDb object from annotations available on a BioMart database |
| makeTxDbFromEnsembl | Make a TxDb object from an Ensembl database |
| makeTxDbFromGFF | Make a TxDb object from annotations available as a GFF3 or GTF file |
| makeTxDbFromGRanges | Make a TxDb object from a GRanges object |
| makeTxDbFromUCSC | Make a TxDb object from annotations available at the UCSC Genome Browser |
| makeTxDbPackage | Making a TxDb package from annotations available at the UCSC Genome Browser, biomaRt or from another source. |
| makeTxDbPackageFromBiomart | Making a TxDb package from annotations available at the UCSC Genome Browser, biomaRt or from another source. |
| makeTxDbPackageFromUCSC | Making a TxDb package from annotations available at the UCSC Genome Browser, biomaRt or from another source. |
| mapFromTranscripts | Map range coordinates between transcripts and genome space |
| mapFromTranscripts-method | Map range coordinates between transcripts and genome space |
| mapIdsToRanges | Map IDs to Genomic Ranges |
| mapIdsToRanges-method | Map IDs to Genomic Ranges |
| mapRangesToIds | Map Genomic Ranges to IDs |
| mapRangesToIds-method | Map Genomic Ranges to IDs |
| mapToTranscripts | Map range coordinates between transcripts and genome space |
| mapToTranscripts-method | Map range coordinates between transcripts and genome space |
| microRNAs | Extract microRNA or tRNA genomic ranges from an object |
| microRNAs-method | Extract microRNA or tRNA genomic ranges from an object |
| nearest-methods | Finding the nearest genomic range neighbor in a TxDb |
| organism-method | TxDb objects |
| pcoverageByTranscript | Compute coverage by transcript (or CDS) of a set of ranges |
| pmapFromTranscripts | Map range coordinates between transcripts and genome space |
| pmapFromTranscripts-method | Map range coordinates between transcripts and genome space |
| pmapToTranscripts | Map range coordinates between transcripts and genome space |
| pmapToTranscripts-method | Map range coordinates between transcripts and genome space |
| promoters | Extract genomic features from a TxDb-like object |
| promoters-method | Extract genomic features from a TxDb-like object |
| select-method | Using the "select" interface on TxDb objects |
| select-methods | Using the "select" interface on TxDb objects |
| seqinfo-method | TxDb objects |
| seqlevels0-method | TxDb objects |
| seqlevels<--method | TxDb objects |
| show-method | TxDb objects |
| species-method | TxDb objects |
| supportedMiRBaseBuildValues | Making a TxDb package from annotations available at the UCSC Genome Browser, biomaRt or from another source. |
| supportedUCSCFeatureDbTables | Making a FeatureDb object from annotations available at the UCSC Genome Browser |
| supportedUCSCFeatureDbTracks | Making a FeatureDb object from annotations available at the UCSC Genome Browser |
| supportedUCSCtables | Make a TxDb object from annotations available at the UCSC Genome Browser |
| threeUTRsByTranscript | Extract and group genomic features of a given type from a TxDb-like object |
| threeUTRsByTranscript-method | Extract and group genomic features of a given type from a TxDb-like object |
| tidyExons | Extract non-overlapping exonic or intronic parts from a TxDb-like object |
| tidyIntrons | Extract non-overlapping exonic or intronic parts from a TxDb-like object |
| tidyTranscripts | Extract non-overlapping exonic or intronic parts from a TxDb-like object |
| transcriptLengths | Extract the transcript lengths (and other metrics) from a TxDb object |
| transcriptLocs2refLocs | Converting transcript-based locations into reference-based locations |
| transcripts | Extract genomic features from a TxDb-like object |
| transcripts-method | Extract genomic features from a TxDb-like object |
| transcriptsBy | Extract and group genomic features of a given type from a TxDb-like object |
| transcriptsBy-method | Extract and group genomic features of a given type from a TxDb-like object |
| transcriptsByOverlaps | Extract genomic features from a TxDb-like object based on their genomic location |
| transcriptsByOverlaps-method | Extract genomic features from a TxDb-like object based on their genomic location |
| transcriptWidths | Converting transcript-based locations into reference-based locations |
| tRNAs | Extract microRNA or tRNA genomic ranges from an object |
| tRNAs-method | Extract microRNA or tRNA genomic ranges from an object |
| TxDb | TxDb objects |
| TxDb-class | TxDb objects |
| UCSCFeatureDbTableSchema | Making a FeatureDb object from annotations available at the UCSC Genome Browser |


Source code for spockbots.output
#!/usr/bin/env pybricks-micropython
import os
from time import sleep
from pybricks import ev3brick as brick
from pybricks.parameters import Color
#######################################################
# READ AND WRITE FILES
#######################################################
debug = True
#######################################################
# READ AND WRITE FILES
#######################################################
[docs]def readfile(name):
"""
Reads the file with the name and returns it as a string.
:param name: The file name
:return: The data in teh file as string
"""
try:
# print ("READ", name)
f = open(name)
data = f.read().strip()
f.close()
return data
except:
return None
[docs]def writefile(name, msg):
"""
Writes a new file with the name. If it exists the
old file will be deleted.
:param name: The name of the file
:param msg: The message to be placed in the file
:return:
"""
# print ("WRITE", name, msg)
# try:
# f = open(name)
# f.write(msg)
# f.close()
# except Exception as e:
# print("FILE WRITE ERROR")
# print(e)
command = 'echo \"' + msg + '\" > ' + name
# print("COMMNAD:", command)
os.system(command)
#######################################################
# Sound
#######################################################
[docs]def beep():
"""
The robot will make a beep
"""
brick.sound.beep()
[docs]def sound(pitch=1500, duration=300):
"""
plays a sound
:param pitch: sound pitch
:param duration: how long the sound plays
:return:
"""
brick.sound.beep(pitch, duration)
#######################################################
# LED
#######################################################
[docs]def led(color):
"""
changes color of led light
:param color: light color
:param brightness: light brightness
:return:
"""
if color == "RED":
led_color = Color.RED
elif color == "GREEN":
led_color = Color.GREEN
elif color == "YELLOW":
led_color = Color.YELLOW
elif color == "BLACK":
led_color = Color.BLACK
elif color == "ORANGE":
led_color = Color.ORANGE
else:
led_color = None
brick.light(led_color)
[docs]def flash(colors=["RED", "BLACK", "RED", "BLACK", "GREEN"],
delay=0.1):
"""
The robot will flash the LEDs and beep twice
"""
beep()
for color in colors:
led(color)
sleep(delay)
beep()
[docs]def signal(t=0.05, pitch=1500, duration=300):
for i in [1,2,3]:
led("YELLOW")
sleep(t)
led("RED")
sound(pitch=pitch, duration=duration)
#######################################################
# LCD
#######################################################
[docs]def clear():
"""
clears display
"""
brick.display.clear()
[docs]def PRINT(*args, x=None, y=None):
"""
prints message on screen at x and y and on the console.
if x and y are missing prints on next position on lcd screen
this message prints test messages.
The sceensize is maximum x=177, y=127)
:param args: multible strings to be printed in between them
:param x: x value
:param y: y value
"""
text = ""
for a in args:
if a is not None:
text = text + str(a) + " "
if x is not None and y is not None:
brick.display.text(text, (x, y))
else:
brick.display.text(text)
print(text)
#######################################################
# Voltage
#######################################################
[docs]def voltage():
"""
prints voltage of battery
"""
value = brick.battery.voltage() / 1000
PRINT("Voltage: " + str(value) + " V", 80, 10)


ALIEN 4 Cloud - 1.4.0 - Documentation
Edit (pull request)Welcome on Alien 4 Cloud documentation. You will find here resources to use alien 4 cloud. This includes:
- Concepts of Alien 4 Cloud
- Installation and configuration
- Creation of cloud services archives (including an overview of OASIS TOSCA concepts)
ALIEN for Cloud High level concept
ALIEN for Cloud (Application LIfecycle ENabler for cloud) is a tool that aims to provide management for enterprise cloud and help enterprise to onboard their applications to a cloud, leverage it’s benefits and, based on project constraints, reach continuous delivery.
As moving to the cloud for an enterprise is a structural change, ALIEN for Cloud leverage the TOSCA standard that is the most advanced and supported standard for the cloud.
The Goal of ALIEN for Cloud is to enable the benefits of a cloud migration in enterprise by easing the DevOps collaboration taking in account the capabilities of each of the IT expert in the enterprise. This is done by providing a single platform where every expert can contribute and share it’s effort and feedback with others.
ALIEN provides three main features:
- Composable PaaS & DevOps collaboration
- Application lifecycle enablement
- Cloud governance
Collaboration
Collaboration in ALIEN for cloud is done by giving the ability to each expert to work on it’s field of expertise, and for other experts to benefits from his work and reuse it in a simple and declarative way. TOSCA standard is a great start point to enable such collaboration. ALIEN for Cloud add user roles management in order to increase the ability to easily collaborate on the platform.
Composable PaaS
Topology definition in ALIEN for cloud
The first aspect of ALIEN for cloud is related to the core of the cloud interoperability: defining an application topology that we can deploy on any cloud. It takes in account critical requirements for an enterprise:
- reusability
- extensibility
- flexibility
- consistency
- evolvability
(Very) Quick introduction to TOSCA
In the TOSCA model, an Application Topology is created by declaration of some components (nodes) instances (templates) based on some existing types. The types defines the meta-model of a component (properties, operations, capabilities and requirements) and it’s implementation artifacts. A TOSCA container can then deploy the declared topology on a cloud and orchestrated it.
Collaboration in a TOSCA model is easy as someone that want’s to build an application topology can reuse components created by the experts. Typically an application architect will be able to reuse software and cloud components defined by the operational teams in the enterprise.
Application lifecycle enablement
Alien 4 Cloud allows users to define multiple versions and environments for an application, each environment has an associated version allowing you to move a version from a development environment to the production environment through all required environments in your lifecycle.
Cloud governance
As ALIEN for cloud manages the topologies of applications as well as their deployments, it keeps many informations that will enable governance of your cloud, a better vision of your applications, their lifecycle, the ability of your projects to deliver fast etc.
It enables features like
- rationalisation of the SI
- capacity planning
- management of middleware support and expiration dates
- etc.


This is heading
This is heading 2 for a class test
This is a paragraph
This is a new color
Google
this is for bold
This tag is for Italic
this is unordered list
list item 1
list item 2
this is a break tag
This is a horizontal line


lareaner profiles. coronavirus. Humans. sponge bob. books. cartoon. the moves I have watch. family. fruits. and the note pad am doing right now Hove /hoʊv/ is a seaside resort and one of the two main parts of the city of Brighton and Hove, along with Brighton. Originally a "small but ancient fishing village" surrounded by open farmland, it grew rapidly in the 19th century in response to the development of its eastern neighbour Brighton, and by the Victorian era it was a fully developed town with borough status. Neighbouring parishes such as Aldrington and Hangleton were annexed in the late 19th and early 20th centuries. In 1997, as part of local government reform, the borough merged with Brighton to form the Borough of Brighton and Hove, and this unitary authority was granted city status in 2000.
boys. trees. bat man. cars. arthur. food. hard labour. Old spellings of Hove include Hou (Domesday Book, 1086), la Houue (1288), Huua (13th century), Houve (13th and 14th centuries), Huve (14th and 15th centuries), Hova (16th century) and Hoova (1675).[2][3] The etymology was disputed at length during the 20th century as academics offered several competing theories. Suggestions included an Old Norse word meaning "hall", "sanctuary" or "barrow", in reference to the Bronze Age barrow near the present Palmeira Square; an Old English phrase æt þæm hofe meaning "at the hall";[note 1] the Old English hufe meaning "shelter" or "covering"; and the Middle English hofe meaning "anchorage". No other places in Britain are called Hove, and single-syllable names as a whole are rare in Sussex.[3] The modern name was originally pronounced "Hoove" (/ˈhuːv/). The present pronunciation (/ˈhoʊv/) "is comparatively recent".


WAL-ACT- pseudoephedrine hydrochloride and triprolidine hydrochloride tablet, film coated
WALGREEN CO.
Disclaimer: Most OTC drugs are not reviewed and approved by FDA, however they may be marketed if they comply with applicable regulations and policies. FDA has not evaluated whether this product complies.
if you are now taking a prescription monoamine oxidase inhibitor (MAOI) (certain drugs for depression, psychiatric or emotional conditions, or Parkinson’s disease), or for 2 weeks after stopping the MAOI drug. If you do not know if your prescription drug contains an MAOI, ask a doctor or pharmacist before taking this product.
corn starch, hypromellose, lactose, magnesium stearate, microcrystalline cellulose, polyethylene glycol, silica gel, stearic acid, titanium dioxide
Well at
Walgreens
WALGREENS PHARMACIST RECOMMENDEDⱡ
NDC 0363-0178-22
Wal-Act®
D Cold & Allergy
Triprolidine HCl / Antihistamine
Pseudoephedrine HCl / Nasal Decongestant
• Relieves runny nose, nasal congestion,
sneezing & itchy, watery eyes
48 TABLETS
(One Tablet Dose)
Actual Size
DISTRIBUTED BY: WALGREEN CO.
200 WILMOT RD., DEERFIELD, IL 60015
Walgreens
100%
SATISFACTION
GUARANTEED
walgreens.com ©2013 Walgreen Co.
ⱡWalgreens Pharmacist Survey Study, November 2012.
50844 REV0612B17822
TAMPER EVIDENT: DO NOT USE IF CARTON IS OPENED OR IF BLISTER UNIT IS TORN, BROKEN OR SHOWS ANY SIGNS OF TAMPERING
Walgreens 44-178
|
WAL-ACT
pseudoephedrine hcl and tripolidine tablet, film coated | ||||||||||||||||||||
| ||||||||||||||||||||
| ||||||||||||||||||||
| ||||||||||||||||||||
| ||||||||||||||||||||
| ||||||||||||||||||||
|
| Labeler - WALGREEN CO. (008965063) |
| Establishment | |||
| Name | Address | ID/FEI | Business Operations |
|---|---|---|---|
| LNK International, Inc. | 038154464 | PACK(0363-0178) |
| Establishment | |||
| Name | Address | ID/FEI | Business Operations |
|---|---|---|---|
| LNK International, Inc. | 832867894 | MANUFACTURE(0363-0178) |