Defines | |
| #define | ADL_ADAPTERCONFIGSTATE_HEADLESS ( 1 << 2 ) |
| #define | ADL_ADAPTERCONFIGSTATE_REQUISITE_RENDER ( 1 << 0 ) |
| #define | ADL_ADAPTERCONFIGSTATE_ANCILLARY_RENDER ( 1 << 1 ) |
| #define | ADL_ADAPTERCONFIGSTATE_SCATTERGATHER ( 1 << 4 ) |
| Indicates that scatter gather feature enabled on the adapter. |
Indicates that the adapter is headless (i.e. no displays can be connected to it)
| #define ADL_ADAPTERCONFIGSTATE_HEADLESS ( 1 << 2 ) |
| #define ADL_ADAPTERCONFIGSTATE_REQUISITE_RENDER ( 1 << 0 ) |
Indicates that the adapter is configured to define the main rendering capabilities. For example, adapters in Crossfire(TM) configuration, this bit would only be set on the adapter driving the display(s).
| #define ADL_ADAPTERCONFIGSTATE_ANCILLARY_RENDER ( 1 << 1 ) |
Indicates that the adapter is configured to be used to unload some of the rendering work for a particular requisite rendering adapter. For eample, for adapters in a Crossfire configuration, this bit would be set on all adapters that are currently not driving the display(s)
| #define ADL_ADAPTERCONFIGSTATE_SCATTERGATHER ( 1 << 4 ) |
Indicates that scatter gather feature enabled on the adapter.


Here is a safe way:
grep -lrIZ foo . | xargs -0 rm -f – -l prints file names of files matching the search pattern. -r performs a recursive search for the pattern foo in the given directory .. If this doesn’t work, try -R. -I (capital i) causes binary files like PDFs to be skipped. -Z ensures that file names are zero- (i.e., nul-)terminated so that a name containing white space does not get interpreted in the wrong way (i.e., as multiple names instead of one). xargs -0 feeds the file names from grep to rm -f, separating words by zero (nul) bytes (remember the -Z option from grep). – is often forgotten but it is very important to mark the end of options and allow for removal of files whose names begin with -. If you would like to see which files are about to be deleted, simply remove the | xargs -0 rm -f – part, and leave off the Z option to grep.


A great zeal for self-learning and solving problems!
I have 5 years of experince in building Web Applications, Machine Leanring and Data Pipeline solutions for clients like Swiggy, Decisions, Tasmanian Government and lot more.
For my work ethics and initiatives, I've been awarded as 'Ace of Initiative' and 'Game Changer'.
You guessed it right, I'm a Computer Science Engineer who finds it difficult to write good intro!
Delivering the awe-inspiring digital transformation experience to clients!
Built Government of Tasmania - Australia's, Seniors Card and Veterans Voucher Program and set up the data ingestion pipeline.
Built 2U's intelligent call manager and interactive dashboard for the sales team.
Building the Team Management Application for 'Church of Nazarene'.
Process Automation under the umbrella of the Center of Excellence(CoE) was established with a vision of Automating and Improving the business process across the organization.
Planned and built multiple in-house Products. Responsible for aiding CC with all their Technical requirements; Requirement Gathering & Analysis, Architecture Design, Process Automation, Automated Reporting, Web Development, Machine Learning, Setting up ETL Pipelines et al.
Owned Internal applications; Resolute and Marvex.
Reduced the expenses amounting to ~25 Cr/Year through continious innvoation.
Trained and mentored junior members!
Generating customer segment and Fraud Segment using K-means algorithm.
The data genrated is used for recommending Refund value.
This project is saving ~Rs.2 Every Order
Predicting the interaction flowing towards CC using data points from Orders, Delivery Platform, Product Goodness etc using XG Boost.
This data is used for Advanced Manpower & Break Management.
Weighted MAPE for the model is 7% as compared to Manual activity which was around 20%
More projects will be added soon.
I enjoy most of my time being outdoors. I love to explore new places with family and friends.
When forced indoors, I follow a number of sci-fi and fantasy genre movies and television shows, I am an aspiring painter, and I spend a large amount of my free time exploring the latest technology advancements in the field of Data Science - Machine Learnig, Deep Learning, Artificial Intelligence & Quantum Computing. The most interesting domains I'm following deeply are Natural Language Understanding & Blockchain.
Just for hobby, I play around with microprocessor | microcontrollers(small scale automation), Racing Bots(Line Follower & obstacle avoidance)


Just got a melodica. Here's my rendition of the Jurassic Park theme song. What do you think? http://www.patricklo.com
jspook1606-Feb-19 07:07 PM
It def could be a whale sis....
Cryptoon06-Feb-19 07:17 PM
if whalesis I would be fine with that
jspook1606-Feb-19 08:02 PM
There were quite a few sisters that capitalized on the last bull run. To me they seem to take profits more efficiently. I just let it run...straight into the ground
Alecandro06-Feb-19 08:03 PM
Next time will be different
Tek06-Feb-19 08:51 PM
I just took my first ever Vitamin D supplement and
I feel it in my head
so it does do something
jspook1606-Feb-19 09:11 PM
Next time... I may let it run to 20 USD
2
ComputerGenie 👴👴👴06-Feb-19 09:11 PM
"whalesis" ffs, as if "whalebro" wasn't silly enough
yorklab06-Feb-19 09:38 PM
Someone just dump into the whale's bid; he's no longer a whale.
Maybe a baby whale.
Lieutenant06-Feb-19 09:42 PM
any other coin when a purchase order of 100btc or more +10 +20% but no kmd.
А couple of months ago whalebro easy bought (no price increase) several million kmd. it's unbelievable.
1
Alecandro06-Feb-19 09:45 PM
someone with that much komodo could surely suppress prices easily if they wanted to though, right?
Cryptoon06-Feb-19 09:47 PM
what if that is what they have been doing
ComputerGenie 👴👴👴06-Feb-19 09:47 PM
Absent the firm belief that it will dip to 16.5, I can't understand who doesn't sell at 18.5 but decides to dump at 17.5
I've seen these spikes down before on XRP, it never really set the direction; just an anomaly. Maybe someone just needed out now and saw an opportunity...........or it could be because I bought a few days ago, that usually causes a dip.(edited)
We post and analyze Japanese court filings on behalf of mtgox creditors. After a five year hiatus we are BACK with new GoxDox.
4
1
Bitcoin Benny07-Feb-19 01:42 PM
@FishyGuts you got the dPoW stuff you needed right?
CryptoNinjaa07-Feb-19 04:06 PM
Anyone know when the kmd>USD market is live ?
on bittrex
modereck07-Feb-19 04:18 PM
it was supposed to be today
ComputerGenie 👴👴👴07-Feb-19 04:19 PM
fwiw, it's currently just after 8 am their time
CryptoNinjaa07-Feb-19 04:31 PM
That makes sense then Genie they are on the opposite side of the "flat plane" to me (edited)
modereck07-Feb-19 04:56 PM
KMD volume increasing...
siu - Chainmakers07-Feb-19 05:01 PM
USD pair might bring some new money
Alecandro07-Feb-19 05:09 PM
i hope so!
FishyGuts07-Feb-19 06:08 PM
@Bitcoin Benny - Yes. I sent KMD pages on dPoW and discussed directly the reasons and exchange would want the coins they list to be covered for many reasons. Confirmation times and Security being the biggest benefits, in addition to all the work being coin team side and not exchange side.
If I ran an exchange...
"10 btc listing fee and security deposit without dPoW, 2 BTC with dPoW"


Click the button below to visit the repo for our site. You can then click the Fork button in the upper-right area of the screen to create a copy of our site in your GitHub account called a fork. Make any changes you want in your fork, and when you are ready to send those changes to us, go to the index page for your fork and click New Pull Request to let us know about it.


|
pyrax
Python Bindings for the Rackspace Cloud
|
This class represents a DNS domain. More...
Public Member Functions | |
| def | delete |
| Deletes this domain and all of its resource records. | |
| def | changes_since |
| Gets the changes for this domain since the specified date/datetime. | |
| def | export |
| Provides the BIND (Berkeley Internet Name Domain) 9 formatted contents of the requested domain. | |
| def | update |
| Provides a way to modify the following attributes of a domain entry: | |
| def | list_subdomains |
| Returns a list of all subdomains for this domain. | |
| def | list_records |
| Returns a list of all records configured for this domain. | |
| def | search_records |
| Returns a list of all records configured for this domain that match the supplied search criteria. | |
| def | find_record |
| Returns a single record for this domain that matches the supplied search criteria. | |
| def | add_records |
| Adds the records to this domain. | |
| def | get_record |
| Gets the full information for an existing record for this domain. | |
| def | update_record |
| Modifies an existing record for this domain. | |
| def | delete_record |
| Deletes an existing record for this domain. | |
Static Public Attributes | |
| add_record = add_records |
This class represents a DNS domain.
| def add_records | ( | self, | |
| records | |||
| ) |
Adds the records to this domain.
Each record should be a dict with the following keys:
| def changes_since | ( | self, | |
| date_or_datetime | |||
| ) |
Gets the changes for this domain since the specified date/datetime.
The date can be one of:
It returns a list of dicts, whose keys depend on the specific change that was made. A simple example of such a change dict:
{u'accountId': 000000, u'action': u'update', u'changeDetails': [{u'field': u'serial_number', u'newValue': u'1354038941', u'originalValue': u'1354038940'}, {u'field': u'updated_at', u'newValue': u'Tue Nov 27 17:55:41 UTC 2012', u'originalValue': u'Tue Nov 27 17:55:40 UTC 2012'}], u'domain': u'example.com', u'targetId': 00000000, u'targetType': u'Domain'}
| def delete | ( | self, | |
delete_subdomains = False |
|||
| ) |
Deletes this domain and all of its resource records.
If this domain has subdomains, each subdomain will now become a root domain. If you wish to also delete any subdomains, pass True to 'delete_subdomains'.
| def delete_record | ( | self, | |
| record | |||
| ) |
Deletes an existing record for this domain.
| def export | ( | self | ) |
Provides the BIND (Berkeley Internet Name Domain) 9 formatted contents of the requested domain.
This call is for a single domain only, and as such, does not provide subdomain information.
Sample export: {u'accountId': 000000, u'contentType': u'BIND_9', u'contents': u'example.com..rackspace.com. '<EMAIL_ADDRESS>1354202974 21600 3600 1814400 500' 'example.com..stabletransit.com.' 'example.com..stabletransit.com.', u'id': 1111111}
| def find_record | ( | self, | |
| record_type, | |||
name = None , |
|||
data = None |
|||
| ) |
Returns a single record for this domain that matches the supplied search criteria.
If no record matches, a DomainRecordNotFound exception will be raised. If more than one matches, a DomainRecordNotUnique exception will be raised.
| def get_record | ( | self, | |
| record | |||
| ) |
Gets the full information for an existing record for this domain.
| def list_records | ( | self, | |
limit = None , |
|||
offset = None |
|||
| ) |
Returns a list of all records configured for this domain.
| def list_subdomains | ( | self, | |
limit = None , |
|||
offset = None |
|||
| ) |
Returns a list of all subdomains for this domain.
| def search_records | ( | self, | |
| record_type, | |||
name = None , |
|||
data = None |
|||
| ) |
Returns a list of all records configured for this domain that match the supplied search criteria.
| def update | ( | self, | |
emailAddress = None , |
|||
ttl = None , |
|||
comment = None |
|||
| ) |
Provides a way to modify the following attributes of a domain entry:
| def update_record | ( | self, | |
| record, | |||
data = None , |
|||
priority = None , |
|||
ttl = None , |
|||
comment = None |
|||
| ) |
Modifies an existing record for this domain.
add_record = add_records [static] |


Subscription name is required.
Subscription name should be maximum 32 characters long.
Subscription name must be minimum 3 characters long.
Only Alphanumeric, spaces and dashes are allowed
Description is required.
Description should be maximum 256 characters long.
Only Alphanumeric, spaces, dashes, underscores, commas & dots are allowed
URL is required.
URL should be maximum 256 characters long.
Invalid URL format.


We sell bitcoin!
- disintermediate turn-key solutions
- seize global e-commerce
- transition mission-critical paradigms
- mesh plug-and-play content
- engineer B2C methodologies
- seize vertical networks
- whiteboard synergistic methodologies
- expedite collaborative metrics
- strategize mission-critical users
- harness front-end channels
- seize leading-edge e-tailers
- exploit clicks-and-mortar synergies
- streamline rich niches


gene maize genes modules network Arabidopsis expression module file development Plant Table Module conserved identified response analysis Additional biosynthesis data cell stress (#), .E- Fig. functions (Additional RNA-Seq related Cell GGM involved {border-style developmental networks datasets different px;} #ffffff;} Gene network, transcription Physiol co-expression leaf transcriptome genes, nitrate S). included plant revealed uptake Arabidopsis, comparison enriched functional organization seed used using Biol endosperm including ligules network. regulator similar (Fig. (pValue Maize based contains pairs potential studies (#) BMC Figure architecture compared encoding function heat homologous homologues identify includes indicates inflorescences master modules, phosphate provide responses wax ./pp.. FPKM Genes Modules Nature PCC Pcor Science Wang contained correlation factor indicating interactions log-transformation-based matrix metabolism selected species values DNA LINK Res Sci constructed control development, dynamics genes. kb) large leaves plants published px; regulators secondary shown starvation transcriptional {font-family ./--- Arabidopsis. Genome TFs analysis. available benzoxazinoids biological clustering example, expressed files font-size future key metabolic metabolism, nitrogen photosynthesis regulatory required runs utilization various ./nature ./tpc.. Additionally, Genet Interestingly, RNA S), Springer binding conservation considered defense development. domestication double; endoplasmic factors flavonoids functioning include interaction interaction(s) mean-variance meristem model non-transformed number nutrient partial pathways pathways. patterns percentage primary process processes protein putative share signaling structure studies. them, tissues type > (PDF ./science. .E-). Acad Acids China Dev GRMZMG, However, Mol Natl Nucleic Proc Schmidt additional analyzed annotation association atlas basic border-color border-width bx, containing data. database dependency deposited discussed enrichment evolutionary fatty fungal glk, high higher homologue important kernels level light like low maize, maize. maturation modules. nutrients oxylipins package previous regulates remains replication reticulum rice roles sequencing shock shows solid; species. storage transport uncharacterized value zein {font-style {font-weight < (Table (encoding ./journal.pone. ./pnas. .E-), AUROC AtGGM Becraft Bioinformatics Buell Development Doebley Downs Freeling GRMZMG Gaussian Hirsch Lee MYB Myers Nat Network Program Research Selected Thus, University WGCNA abiotic acid anthocyanin anti-fungal article assimilation biology bold calculated coexpression compartments construction content controls corresponding courier; designated differences distinct em; encode encodes example family floral gene’s graphical group heatmap highly inflorescence likely log-transformed lox, mainly major module, mutants new novel nucleosome organ organization, original oxylipins, participate previously procedure program pt;} red regulation response. resulting results shared similarity specific supplementary terms transporter utilization, variety well, well.


Managing Connections¶
Airflow needs to know how to connect to your environment. Information
such as hostname, port, login and passwords to other systems and services is
handled in the Admin->Connections
section of the UI. The pipeline code you
will author will reference the ‘conn_id’ of the Connection objects.
Connections can be created and managed using either the UI or environment variables.
See the Connenctions Concepts documentation for more information.
Creating a Connection with the UI¶
Open the Admin->Connections
section of the UI. Click the Create
link
to create a new connection.
- Fill in the
Conn Id
field with the desired connection ID. It is recommended that you use lower-case characters and separate words with underscores. - Choose the connection type with the
Conn Type
field. - Fill in the remaining fields. See Connection Types for a description of the fields belonging to the different connection types.
- Click the
Save
button to create the connection.
Editing a Connection with the UI¶
Open the Admin->Connections
section of the UI. Click the pencil icon next
to the connection you wish to edit in the connection list.
Modify the connection properties and click the Save
button to save your
changes.
Creating a Connection with Environment Variables¶
Connections in Airflow pipelines can be created using environment variables.
The environment variable needs to have a prefix of AIRFLOW_CONN_
for
Airflow with the value in a URI format to use the connection properly.
When referencing the connection in the Airflow pipeline, the conn_id
should be the name of the variable without the prefix. For example, if the
conn_id
is named postgres_master
the environment variable should be
named AIRFLOW_CONN_POSTGRES_MASTER
(note that the environment variable
must be all uppercase). Airflow assumes the value returned from the
environment variable to be in a URI format (e.g.
postgres://user:password@localhost:5432/master
or
s3://accesskey:secretkey@S3
).
Connection Types¶
Google Cloud Platform¶
The Google Cloud Platform connection type enables the GCP Integrations.
Authenticating to GCP¶
There are two ways to connect to GCP using Airflow.
- Use Application Default Credentials, such as via the metadata server when running on Google Compute Engine.
- Use a service account key file (JSON format) on disk.
Default Connection IDs¶
The following connection IDs are used by default.
bigquery_default
- Used by the
BigQueryHook
hook. google_cloud_datastore_default
- Used by the
DatastoreHook
hook. google_cloud_default
- Used by the
GoogleCloudBaseHook
,DataFlowHook
,DataProcHook
,MLEngineHook
, andGoogleCloudStorageHook
hooks.
Configuring the Connection¶
- Project Id (required)
- The Google Cloud project ID to connect to.
- Keyfile Path
Path to a service account key file (JSON format) on disk.
Not required if using application default credentials.
- Keyfile JSON
Contents of a service account key file (JSON format) on disk. It is recommended to Secure your connections if using this method to authenticate.
Not required if using application default credentials.
- Scopes (comma separated)
A list of comma-separated Google Cloud scopes to authenticate with.
Note
Scopes are ignored when using application default credentials. See issue AIRFLOW-2522.
MySQL¶
The MySQL connect type allows to connect with MySQL database.
Configuring the Connection¶
- Host (required)
- The host to connect to.
- Schema (optional)
- Specify the schema name to be used in the database.
- Login (required)
- Specify the user name to connect.
- Password (required)
- Specify the password to connect.
- Extra (optional)
Specify the extra parameters (as json dictionary) that can be used in mysql connection. The following parameters are supported:
- charset: specify charset of the connection
- cursor: one of “sscursor”, “dictcursor, “ssdictcursor” - specifies cursor class to be used
- local_infile: controls MySQL’s LOCAL capability (permitting local data loading by clients). See MySQLdb docs for details.
- unix_socket: UNIX socket used instead of the default socket
- ssl: Dictionary of SSL parameters that control connecting using SSL (those parameters are server specific and should contain “ca”, “cert”, “key”, “capath”, “cipher” parameters. See MySQLdb docs for details. Note that in order to be useful in URL notation, this parameter might also be a string where the SSL dictionary is a string-encoded JSON dictionary.
Example “extras” field:
{ "charset": "utf8", "cursorclass": "sscursor", "local_infile": true, "unix_socket": "/var/socket", "ssl": { "cert": "/tmp/client-cert.pem", "ca": "/tmp/server-ca.pem'", "key": "/tmp/client-key.pem" } }
or
{ "charset": "utf8", "cursorclass": "sscursor", "local_infile": true, "unix_socket": "/var/socket", "ssl": "{\"cert\": \"/tmp/client-cert.pem\", \"ca\": \"/tmp/server-ca.pem\", \"key\": \"/tmp/client-key.pem\"}" }
When specifying the connection as URI (in AIRFLOW_CONN_* variable) you should specify it following the standard syntax of DB connections, where extras as passed as parameters of the URI (note that all components of the URI should be URL-encoded).
For example:
mysql://mysql_user:XXXXXXXXXXXX@<IP_ADDRESS>:3306/mysqldb?ssl=%7B%22cert%22%3A+%22%2Ftmp%2Fclient-cert.pem%22%2C+%22ca%22%3A+%22%2Ftmp%2Fserver-ca.pem%22%2C+%22key%22%3A+%22%2Ftmp%2Fclient-key.pem%22%7D
Note
If encounter UnicodeDecodeError while working with MySQL connection check the charset defined is matched to the database charset.


vignettes/advanced_usage.Rmd
advanced_usage.Rmd
This vignette will focus on a few more intricate features of the pharmaRTF package. After reviewing this document, you should have a good idea of how to get the most out of pharmaRTF. Specifically, this vignette covers:
Some of the syntax we use throughout this document uses the %>%
pipe operator. This is to display support for a tidyverse style of coding. You can find the %>%
operator in the magittr package.
In development of this feature, we realized as a team that the orientation of an RTF document has a bit of room for confusion. This spawns from the fact that within Microsoft Word, orientation is automatically determined by the document height and width, despite there being a keyword within RTF syntax that specifies landscape orientation. That said, we believe the most intuitive way to set the orientation of a document is with a property function, which in pharmaRTF is simply orientation()
/set_orientation()
.
The default orientation of a pharmaRTF
document is landscape, as this is typically what you would use on the clinical reports that the package is designed for. orientation
is closely tied with the page_size
attribute. When the orientation of an rtf_doc
object is set to landscape, the height and width of the pagesize
attribute will write out as specified in the object, with height
writing to the height document property and width
writing to the width property.
ht <- huxtable::as_hux(iris, add_colnames=TRUE) %>% huxtable::set_width(1.2) doc <- rtf_doc(ht) pagesize(doc) #> width height #> 11.0 8.5
When you switch the orientation to ‘portrait’, the height and width properties will not change. Rather, when the actual RTF document is written out, the height and width will be reversed, effectively flipping the document on its side.
doc <- rtf_doc(ht) %>% # Set orientation to portrait set_orientation('portrait') # Page size does not change pagesize(doc) #> width height #> 11.0 8.5
So why not switch the height and width properties in the object? This opens the door for inadvertent confusion. Consider the case where a user changes the orientation of the document. At that point, assume you switched the height and width. Next, the user manually sets height and width themselves. At this point, the change in orientation would be overridden by whatever height and width the user chooses manually. This is why we decided to only have the reversal happen at the time of writing the RTF code. Note that height and width will always align with the object default, which is landscape. But the document itself will write out with portrait orientation.
After changing the orientation, you can see that the height and the width have switched in the output document, and the document is in portrait orientation
A common requirement of tables is to have spanning column headers. When columns need to be grouped in presentation, this is common practice. This requires a combination of work within huxtable and pharmaRTF. The first thing you need to do is create your huxtable object. For more details on how to do this, see the huxtable tips vignette.
# Create the column headers data frame column_headers <- data.frame( Species = c("", "Species of Flower"), Sepal.Length = c("Sepal", "Length"), Sepal.Width = c("", "Width"), Petal.Length = c("Petal", "Length"), Petal.Width = c("", "Width"), stringsAsFactors = FALSE ) # Create the huxtable table ht <- huxtable::as_hux(rbind(column_headers, iris)) %>% # Merge the Sepal cell over the Length and Width huxtable::merge_cells(1, 2:3) %>% # Merge the Petal cell over the Length and Width huxtable::merge_cells(1, 4:5) %>% # Align the top cells for both Sepal and Petal huxtable::set_align(1,2, 'center') %>% huxtable::set_align(1,4, 'center') %>% # Bold all the column header rows huxtable::set_bold(1:2, 1:ncol(iris), TRUE) %>% # Bottom border on 1st column header row huxtable::set_bottom_border(1, 2:4, 1) %>% # Bottom border on 2nd row huxtable::set_bottom_border(2, 1:ncol(iris), 2) %>% # Set the page width huxtable::set_width(1.5) ht[1:10,]
| Species | Sepal.Length | Petal.Length | ||
|---|---|---|---|---|
| Sepal | Petal | |||
| Species of Flower | Length | Width | Length | Width |
| setosa | 5.1 | 3.5 | 1.4 | 0.2 |
| setosa | 4.9 | 3 | 1.4 | 0.2 |
| setosa | 4.7 | 3.2 | 1.3 | 0.2 |
| setosa | 4.6 | 3.1 | 1.5 | 0.2 |
| setosa | 5 | 3.6 | 1.4 | 0.2 |
| setosa | 5.4 | 3.9 | 1.7 | 0.4 |
| setosa | 4.6 | 3.4 | 1.4 | 0.3 |
Once the huxtable table is created with your multiple rows of column headers, incorporating it into your rtf_doc
object is simple. Just use the header_rows
argument when creating your RTF doc.
Below you can see that the 2 rows of column headers have been pulled into the header of the document and are repeating from page to page.
New in pharmaRTF v0.1.1, header_rows
now additionally offers the capability to prevent column headers from being pulled into the RTF document header. You can do this as follows:
# Method 1 doc <- rtf_doc(ht, header_rows=0) # Method 2 doc <- rtf_doc(ht) %>% set_header_rows(0) write_rtf(doc, file="table6.rtf")
An odd quirk of RTF documents is the method in which they do cell padding. The default output actually uses a minimal amount of cell padding, but when looking at your display, it may still be too large for your personal preference of the display. But fear not! We have a method to help minimize the cell padding further.
The root of the issue is that RTF documents have two methods for handling cell padding. You can read more about this within the Details section of the ignore_cell_padding()
function. From a user perspective, it is simply a matter of adding one more line into the creation of your rtf_doc
object.
doc <- rtf_doc(ht, header_rows=2) %>% set_ignore_cell_padding(TRUE) # Or avoiding piping ignore_cell_padding(doc) <- TRUE write_rtf(doc, file="table7.rtf")
Depending your display, you may want to have a gap between your titles and the column headers, or potentially space below the column headers and the start of the body of the table. One way to deal with this could be to add blank title lines or blank rows to your table - but that would be a hacky fix and less than ideal. This is why the column_header_buffer
attribute exists in the rtf_doc
object.
column_header_buffer()
sets the buffer of spaces you want above and below the column headers.
doc <- rtf_doc(ht, header_rows=2) %>% set_ignore_cell_padding(TRUE) %>% set_column_header_buffer(top=2, bottom=1) %>% add_titles(hf_line("The Iris Dataset", bold=TRUE, font_size=20)) write_rtf(doc, file="table8.rtf")
Very often, we have tiles in clinical reports where there’s text that flushes left and right on the same line. pharmaRTF has a method to handle this within the hf_line
object for titles and footnotes. hf_line
objects have two spaces available within the text
element:
hf_line('Text1', 'Text2') #> $text #> [1] "Text1" "Text2" #> #> attr(,"align") #> [1] "center" #> attr(,"bold") #> [1] FALSE #> attr(,"italic") #> [1] FALSE #> attr(,"font") #> [1] NA #> attr(,"font_size") #> [1] NA #> attr(,"index") #> [1] NA #> attr(,"class") #> [1] "hf_line"
When the alignment is set to center, left, or right, these elements will simply concatenate. But when the alignment is set to ‘split’, the first text alignment will align on the left and the second on the right. This enables you to do those split titles and footnotes that you will often see within reports.
doc <- rtf_doc(ht, header_rows=2) %>% add_titles(hf_line("I'm on the left", "I'm on the right", bold=TRUE, align='split')) write_rtf(doc, file="table9.rtf")
The hf_line
object has three keywords that trigger special behavior within titles and footnotes. These are:
When the text of a title/footnote starts with these keywords (note that it must start with this text), it triggers a special action. The text can either be in the first or second text element. Each one of these warrants some further explanation on their own.
The PAGE_FORMAT:
keyword triggers page numbering within a title or a footnote. This format can display both the current page and the total number of pages in the document. The user has full control over how this display happens, except for the fact that the current page must come first. Adding total pages is optional, but it has to be after the current page.
To add the page numbers into your display, you simply specify the keyword within the text element of an hf_line
object, followed by your desired format. Enter %s
where you want the page numbers to display. For example, let’s say you want to specify a page format like Page 1 of 12
. To do this in your title or footnote, you would enter:
hf_line('PAGE_FORMAT: Page %s of %s")
Similarly, let’s say you wanted you page numbering to look like 1 | 5
:
hf_line('PAGE_FORMAT: %s | %s")
Or what if you just wanted Page 5
?
hf_line('PAGE_FORMAT: Page %s")
Whatever text you specify, the first occurrence of %s
will be replaced with the current page, and the second occurrence will be replaced with the total. Looking at how this appears in the display:
doc <- rtf_doc(ht, header_rows=2) %>% add_titles(hf_line("PAGE_FORMAT: Page %s of %s", bold=TRUE, align='right')) write_rtf(doc, file="table10.rtf")
This also works within split titles:
doc <- rtf_doc(ht, header_rows=2) %>% add_titles(hf_line("Text on the left", "PAGE_FORMAT: Page %s of %s", bold=TRUE, align='split')) write_rtf(doc, file="table11.rtf")
Another standard practice is to include the run time of a document within the report, perhaps in a footnote. The DATE_FORMAT: keyword allows you to do this, writing the program execution time while the RTF document is being written out.
Date formats are specified using the standard R date formatting tokens. A full list of those tokens and their meaning can be found here. Similar to PAGE_FORMAT:, as the user, you have full control over how the date is specified, and can include any other text you desire within the string.
NOTE: Date-times displayed will be in UTC. We have not yet added the capability to display the time within a specified locale.
As a practical example, consider entering an ISO-8601 complaint date-time:
hf_line("DATE_FORMAT: %Y-%m-%dT%H:%M:%S")
Viewing this within a display, we can see that the time decodes properly.
doc <- rtf_doc(ht, header_rows=2) %>% add_titles(hf_line("Text on the left", "DATE_FORMAT: %Y-%m-%dT%H:%M:%S", bold=TRUE, align='split')) write_rtf(doc, file="table12.rtf")
The formats have more flexibility as well, including display day of the week, full months, etc.
doc <- rtf_doc(ht, header_rows=2) %>% add_titles(hf_line("Text on the left", "DATE_FORMAT: Document run on %H:%M %A, %B %d, %Y", bold=TRUE, align='split')) write_rtf(doc, file="table13.rtf")
The last of the special formats is FILE_PATH:. This keyword allows you to display the location of the executing R script automatically. This allows traceability of the display to the originating file, which can be desirable in many processes. That said, there’s a bit of nuance to the functionality of the is keyword.
The location of an executing R script is not as intuitive as it may seem. This is because there are multiple ways that an R script can be executed:
source()
commandRscript
command through the command lineThe file path will be determined in the above hierarchy. The only two options above that can return an actual file path are the source()
command and running via Rscript
. When a file is run interactively, there is no guarantee of the executing files location - because the code is detached from the actual file. Therefore, in these cases, the text <run_interactively>
will be returned.
Using the FILE_PATH: keyword, simply use the token %s
to specify where you want the file path to appear. Like the other keywords, you may also include other text in the output string.
doc <- rtf_doc(ht, header_rows=2) %>% add_titles(hf_line("Text on the left", "FILE_PATH: Run from: %s", bold=TRUE, align='split')) write_rtf(doc, file="table14.rtf")
As an example of a populated path:
source('file_path_example.r')
If you have not already reviewed them, be sure to check out our other vignettes!
vignette("pharmaRTF")
vignette("huxtable_tips")
vignette("advanced_usage")


If you want someone to write a program for you, a first
milestone might be to submit a proposed software architecture.
If you want logo design, a first milestone might be a sketch
of the concept.
If you want translation services, a first milestone might be a
translation of the first five minutes of content.
If you want a singer, a first milestone might be a quick
recording of just your chorus.
What do you expect from this milestone?
Upload files and worker details that will be required to complete the task
No files necessary
Dropbox
Google Drive
No spreadsheet, use my own web page
Now you are ready to create the prototype task, click NEXT to use the design board


DBC Fireside Chat
Am I a Chef or a Diner?
11-21-2014
I just finished watching the entire Fireside Chat with Shareef, and I loved what I saw. This is the reason why I chose DBC over the other bootcamps that are out there (I love how Shareef referred to the majority of the other bootcamps as a "joke"). I love the tenets that DBC runs on. It is this type of culture that I thrive in the best. The idea of camaraderie between classmates, that everyone is in this together, one for all and all for one; that all really appeals to me. I know there are going to be moments where I need to lean on one of my cohort mates for something, and I'm hoping that they will view me as someone that they can lean on as well.
I remember the "kitchen vs restaurant" analogy from one of the videos I watched before applying, and it really resonated with me. There was a time when my mindset was definitely that of the "restaurant" viewpoint. In high school and even college, I expected to go to class and have the information force-fed to me for later regurgitation. DBC has taught me that learning new information is a two-way street. You can't expect to be able to just take in the information that is taught and store it so that you can use it later. We are not just classmates, we are a team. Everyone has to take partial responsibility in the learning and development of others, and if we do that, we will all be better off in the long run.
I have been nervous from the beginning that I was going to be behind most of the people in the class. Now I know that this will not be the case. There will be plenty of other beginners like myself, as well as people who are more advanced. We will all be able to teach each other something. While someone who is more technologically advanced than myself might be able to teach me things I didn't know in that realm, I may be able to teach them something culturally about different ways to learn that they hadn't thought about before. Everyone in this program has something to offer, and that's an important thing to remember. I am doing my best to expose and embrace my ignorance, something I've had trouble doing in the past. I always felt like I needed to prove that I knew things that I actually didn't, and that won't work here. There is so much that I don't know, and if I don't expose that and ask for help, then I won't be able to get anywhere in DBC.
All of this being said, I could not be more excited to continue my prep work and learn everything I can before beginning Phase 1. I know it is going to be a bumpy road with lots of ups and downs, but if we all stay focused on what we need to accomplish and concentrate on the best ways to get us to our destination, it will help make the ride as smooth as possible.


US: Five-year-old boy takes dad’s heroin to school, says it makes him a superhero
by Lee Brown(NEW YORK POST) — A 5-year-old boy took a superhero-stamped baggie of his dad’s heroin to his Massachusetts kindergarten — telling teachers it turned him into Spider-Man when he tasted it, according to a report.
The youngster sparked alarm at the H.B. Lawrence Elementary School in Holyoke last Thursday after showing off the baggie with a stamp of the Marvel superhero, officials told the Daily Hampshire Gazette.
After his apparent confession about tasting it — telling teachers he had put it in his mouth — the boy was raced to Baystate Medical Center in Springfield, the report says. He appeared healthy and officials believe he may have escaped ingesting any of the drug from the sealed bag.
“[The boy] loves Spider-Man,” Holyoke Police Lt. James Albert told the paper. “Our officers were quite taken by it all. You don’t often deal with this.”
His 29-year-old dad, Benny Garcia, was arrested after officers found him sleeping in bed on top of numerous other bags holding the same white powder, according to the paper.
“The officers located the same sort of baggie (of) heroin stamped ‘Spider-Man’ that the child brought to school in a dresser drawer of the defendant’s bedroom,” Assistant District Attorney Matthew Green said in court, calling it “a particularly shocking and egregious” case.
Police found at least 170 baggies of heroin as well as baggies and Ziploc bags of cocaine, the paper said, citing court documents.
When officers told Garcia what happened to his son he became “very emotional,” according to the court documents.
Garcia pleaded not guilty to charges of drug possession and reckless endangerment of a child, the report said. Judge William Rota ordered him held until a dangerousness hearing scheduled for Nov. 20.
The boy and an infant sibling were removed from the family home by the Department of Children and Families, the report said.
More International News Stories
-
‘Iranian Hulk’ Sajad Gharibi joins Bare Knuckle Fighting Championship November 17, 2019
-
US: The kinky secrets found inside Pablo Escobar’s private chambers November 12, 2019
-
US: Slain college student Alexis Crawford was close friends with ‘killer’ roommate, family says November 12, 2019
-
Professor dismembered student-turned-lover, planned to kill himself dressed as Napoleon November 11, 2019
-
Texas man allegedly killed mom’s dog because he couldn’t have sex in the house November 11, 2019
-
Doctor allegedly performed hysterectomies without consent November 11, 2019
-
‘Get down!’: Mother’s last words to her kids before Mexican cartel slayings November 11, 2019
-
8-year-old boy steers car to safety after mom has seizure behind wheel November 11, 2019
-
Internet pours out support for autistic man who asked ‘Would someone like me?’ November 11, 2019


#include <PxVehicleComponents.h>
◆ PxVehicleDifferentialNWData() [1/2]
| PxVehicleDifferentialNWData::PxVehicleDifferentialNWData |
( |
| ) |
|
|
inline |
◆ PxVehicleDifferentialNWData() [2/2]
| PxVehicleDifferentialNWData::PxVehicleDifferentialNWData |
( |
const PxEMPTY |
| ) |
|
|
inline |
◆ getDrivenWheelStatus()
| PxU32 PxVehicleDifferentialNWData::getDrivenWheelStatus |
( |
| ) |
const |
◆ getIsDrivenWheel()
| bool PxVehicleDifferentialNWData::getIsDrivenWheel |
( |
const PxU32 |
wheelId | ) |
const |
Test if a specific wheel has been configured as a driven or non-driven wheel.
◆ isValid()
| bool PxVehicleDifferentialNWData::isValid |
( |
| ) |
const |
|
private |
◆ setDrivenWheel()
| void PxVehicleDifferentialNWData::setDrivenWheel |
( |
const PxU32 |
wheelId, |
|
|
const bool |
drivenState |
|
) |
| |
Set a specific wheel to be driven or non-driven by the differential.
- Note
- The available drive torque will be split equally between all driven wheels. Zero torque will be applied to non-driven wheels. The default state of each wheel is to be uncoupled to the differential.
◆ setDrivenWheelStatus()
| void PxVehicleDifferentialNWData::setDrivenWheelStatus |
( |
PxU32 |
status | ) |
|
◆ PxVehicleDriveSimDataNW
◆ PxVehicleUpdate
| friend class PxVehicleUpdate |
|
friend |
◆ mBitmapBuffer
◆ mInvNbDrivenWheels
| PxReal PxVehicleDifferentialNWData::mInvNbDrivenWheels |
|
private |
◆ mNbDrivenWheels
| PxU32 PxVehicleDifferentialNWData::mNbDrivenWheels |
|
private |
◆ mPad
| PxU32 PxVehicleDifferentialNWData::mPad |
|
private |
The documentation for this class was generated from the following file:


| For immediate release |
The Federal Reserve today announced the following set of policy actions:
Growing caution by lenders and unsettled conditions in financial markets more generally are likely to be restraining aggregate demand in the future. Against this backdrop, further easing of the stance of monetary policy was judged to be warranted to sustain economic growth in the context of contained inflation. In taking the discount rate action, the Board approved requests submitted by the Boards of Directors of the Federal Reserve Banks of New York, Philadelphia, Atlanta, Chicago, St. Louis, Minneapolis, Kansas City, and San Francisco. The discount rate is the interest rate that is charged depository institutions when they borrow from their district Federal Reserve Banks. |


Loading()...
NOT Connected...
Machine: {{ serialServer.getMachine().description }}
Erase Eeprom
Write to machine
Read Eeprom from machine
Info (read only)
Number of Axis
Use Axis
Command Syntax
{{ECommandSyntax[key]}}
WorkOffset Count
Has Spindle
Has Analog Spindle
Has Spindle Direction
Has Coolant
Has Probe
Has SD
hasEeprom
Can Rotate
Has Hold
Has Resume
Has Hold/Resume
Has Kill
Is Laser
Dtr Is Reset
Need EEprom Flush
General
Max StepRate
Error
Acc
Number is required.
Min.
Dec
Error
Jerk Speed
Error
RefMove StepRate
Error
Move Away from Reference
Error
Steps Per Mm1000
Error
Max Spindle Speed
Error
Spindle Fade Time
Error
Stepper Off Timeout
Error
Ref-Sequence:{{i+1}}
{{EReverenceSequence[key]}}
Plotter
Pen Down Feedrate
Error
Pen Up Feedrate
Error
Move PenDown Feedrate
Error
Move PenUp Feedrate
Error
Move PenChange Feedrate
Error
PenDown Pos
Error
PenUp Pos
Error
PenChange Pos X
Error
PenChange Pos Y
Error
PenChange Pos Z
Error
PenChange Pos X-Ofs
Error
PenChange Pos Y-Ofs
Error
Clamp Open Pos
Error
Clamp Close Pos
Error
Clamp Open Delay
Error
Clamp Close Delay
Error
{{machineControlState.toAxisName(i)}}:
Size
Error
Ref Move Type
{{EReverenceType[key]}}
Stepper Direction
Ref Hit Value (Min)
Ref Hit Value (Max)
Max StepRate
Acc
Dec
Steps Per Mm1000
RefMove StepRate
Init Position
Probe Size


Reverse Computation Bitfield. More...
#include <ross-types.h>
Data Fields | |
| unsigned int | c0:1 |
| unsigned int | c1:1 |
| unsigned int | c2:1 |
| unsigned int | c3:1 |
| unsigned int | c4:1 |
| unsigned int | c5:1 |
| unsigned int | c6:1 |
| unsigned int | c7:1 |
| unsigned int | c8:1 |
| unsigned int | c9:1 |
| unsigned int | c10:1 |
| unsigned int | c11:1 |
| unsigned int | c12:1 |
| unsigned int | c13:1 |
| unsigned int | c14:1 |
| unsigned int | c15:1 |
| unsigned int | c16:1 |
| unsigned int | c17:1 |
| unsigned int | c18:1 |
| unsigned int | c19:1 |
| unsigned int | c20:1 |
| unsigned int | c21:1 |
| unsigned int | c22:1 |
| unsigned int | c23:1 |
| unsigned int | c24:1 |
| unsigned int | c25:1 |
| unsigned int | c26:1 |
| unsigned int | c27:1 |
| unsigned int | c28:1 |
| unsigned int | c29:1 |
| unsigned int | c30:1 |
| unsigned int | c31:1 |
tw_bf Some applications find it handy to have this bitfield when doing reverse computation. So we follow GTW tradition and provide it.
Definition at line 178 of file ross-types.h.
| unsigned int tw_bf::c0 |
Definition at line 179 of file ross-types.h.
| unsigned int tw_bf::c1 |
Definition at line 180 of file ross-types.h.
Referenced by phold_event_handler(), and phold_event_handler_rc().
| unsigned int tw_bf::c10 |
Definition at line 189 of file ross-types.h.
| unsigned int tw_bf::c11 |
Definition at line 190 of file ross-types.h.
| unsigned int tw_bf::c12 |
Definition at line 191 of file ross-types.h.
| unsigned int tw_bf::c13 |
Definition at line 192 of file ross-types.h.
| unsigned int tw_bf::c14 |
Definition at line 193 of file ross-types.h.
| unsigned int tw_bf::c15 |
Definition at line 194 of file ross-types.h.
| unsigned int tw_bf::c16 |
Definition at line 195 of file ross-types.h.
| unsigned int tw_bf::c17 |
Definition at line 196 of file ross-types.h.
| unsigned int tw_bf::c18 |
Definition at line 197 of file ross-types.h.
| unsigned int tw_bf::c19 |
Definition at line 198 of file ross-types.h.
| unsigned int tw_bf::c2 |
Definition at line 181 of file ross-types.h.
| unsigned int tw_bf::c20 |
Definition at line 199 of file ross-types.h.
| unsigned int tw_bf::c21 |
Definition at line 200 of file ross-types.h.
| unsigned int tw_bf::c22 |
Definition at line 201 of file ross-types.h.
| unsigned int tw_bf::c23 |
Definition at line 202 of file ross-types.h.
| unsigned int tw_bf::c24 |
Definition at line 203 of file ross-types.h.
| unsigned int tw_bf::c25 |
Definition at line 204 of file ross-types.h.
| unsigned int tw_bf::c26 |
Definition at line 205 of file ross-types.h.
| unsigned int tw_bf::c27 |
Definition at line 206 of file ross-types.h.
| unsigned int tw_bf::c28 |
Definition at line 207 of file ross-types.h.
| unsigned int tw_bf::c29 |
Definition at line 208 of file ross-types.h.
| unsigned int tw_bf::c3 |
Definition at line 182 of file ross-types.h.
| unsigned int tw_bf::c30 |
Definition at line 209 of file ross-types.h.
| unsigned int tw_bf::c31 |
Definition at line 210 of file ross-types.h.
| unsigned int tw_bf::c4 |
Definition at line 183 of file ross-types.h.
| unsigned int tw_bf::c5 |
Definition at line 184 of file ross-types.h.
| unsigned int tw_bf::c6 |
Definition at line 185 of file ross-types.h.
| unsigned int tw_bf::c7 |
Definition at line 186 of file ross-types.h.
| unsigned int tw_bf::c8 |
Definition at line 187 of file ross-types.h.
| unsigned int tw_bf::c9 |
Definition at line 188 of file ross-types.h.


Bumped into this issue twice and because the first time it happened was almost a year ago, in different project, I'd already lost my mental note about it when it happened again for second time. Our views functions are wrapped inside @transaction.commit_manually
, which look like below:-
@transaction.commit_manually
def send_message(request):
context = {}
# do some stuff
transaction.commit()
return render(request, 'path/to/template.html', context)
This work flawlessly until recently, I need to add some logic in the template that need to check certain user's permission, before displaying the part. In the template, it just some function call that access db like:-
{% if user.can_see_this %}
Some link
{% endif %}
Django now raise TransactionManagementError
complaining I have pending commit/rollback. It doesn't make sense because I can verify that the line that executed transaction.commit()
was reached in the views above. Only after reading through this ticket on django issue tracker, I'd immediately remember the real issue.
Turn out this caused by new behavior of django transaction in 1.3 and above. Before 1.3, transaction only marked as dirty if we did any write database operation but since 1.3 and above, any database operation will mark the transaction as dirty. So the following code
will work before 1.3:-
@transaction.commit_manually
def sendmessage(request):
transaction.rollback()
user = User.objects.get(pk=1)
return HttpResponse('OK')
All database operation now will mark the transaction as dirty and since we access the db in template - which happened during render after we called commit(), it obvious now why django complain we unclosed transaction.
It should be written like below:-
@transaction.commit_manually
def send_message(request):
context = {}
# do some stuff
response = render(request, 'path/to/template.html', context)
transaction.commit()
return response


Cheshire3 Object Model: Class SrbConnection |
object --+ | SrbConnection
|
__init__(self,
host,
port,
domain,
auth="ENCRYPT1",
user="",
passwd="",
dn="")
x.__init__(...) initializes x; see x.__class__.__doc__ for signature |
|
| disconnect(self) | |
| open(self, name, flag='w') | |
| create(self, name, size=-1, type="generic", resource="", path="") | |
| create_collection(self, name) | |
| up_collection(self) | |
| open_collection(self, name) | |
| delete_collection(self, recursive=0) | |
| n_subcollections(self) | |
| n_objects(self) | |
| object_metadata(self, idx, type='name') | |
| collection_name(self, idx) | |
| walk_names(self) | |
| walk(self) | |
| rmrf(self) | |
|
Inherited from |
| id | |
| collection | |
| resource | |
| host | |
| port | |
| domain | |
| auth | |
| user | |
| passwd | |
| dn | |
|
Inherited from |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
id
|
collection
|
resource
|
host
|
port
|
domain
|
auth
|
user
|
passwd
|
dn
|
| Generated by Epydoc 3.0alpha2 on Wed Aug 9 18:10:00 2006 | http://epydoc.sf.net |


Additional scripts to analyze the data
This is a wrapper above a GPU-assisted molecular dynamics package Openmm.
You can find extensive description of openmm classes here: https://simtk.org/api_docs/openmm/api10/annotated.html
The main library is located in openmmlib.Simulation
A file knotAnalysis.py contains code needed to calculate Alexander’s polynomials, a measure of knot complexity. It also uses OpenMM to help unwrap polymer and reduce time needed to calculate Alexander’s polynomial
A file polymerScalings.py has some utilities to calculate Rg(s) and Pc(s) for polymer conformations in a fast and efficient way.
A file contactmaps.py has code to quickly calculate contacts within a polymer structure, and organize them as contactmaps. It is used by polymerScalings.
A file pymol_show has utilities to visualize polymer conformations using pymol
Polymer configuration is represented as a Nx3 numpy array of coordinates. Start/end of chains/rings are not directly specified in the file, and have to be added through method setLayout
Input file may have the simplistic format, described in txtToJoblib.py (first line with number of particles, then N lines with three floats corresponding to x,y,z coordinates each). Input file can also be any of the output files.
Output file format is a dictionary, saved with joblib.dump. Nx3 data array is stored under the key “data”. The rest of the dictionary consists of metadata, describing details of the simulation. This metadata is for informative purpose only, and is ignored by the code.
All forces of the system are added by the code to the self.ForceDict dictionary. After the force is added, the class (or user) can get it out of the self.ForceDict and modify the force. Once the simulation is started, all forces are automatically applied and cannot be modified.
Two types of bond forces are harmonic bond force and FENE-type bond as described in Grosberg papers. Individual bonds can be added using addBond, while polymer bonds can be added using addHarmonicPolymerBonds, etc.
Grosberg repulsive force - a faster and better implementation of repulsive force; and LennardJones Force, that can be attractive and allows to specify extra attraction/repulsion between any pairs of particles.
There are also polynomial repulsive and attractive forces which are faster due to a shorter cutoff radius.
Stiffness force can be harmonic, or the “special” Grosberg force, kept for compatibility with the systems used in Grosberg forces
External forces include spherical confinement, cylindrical confinement, attraction to “lamina”- surface of a cylinder, gravity, etc.
A sample line of information printed on each step looks like this:
minim bl=5 (i) pos[1]=[99.2 52.1 52.4] dr=0.54 kin=3.65 pot=3.44 Rg=107.312 SPS=144:
Let’s go over it step by step.
minim - simulation name (sim -default, minim - energy minimization. Other name can be provided in self.name).
bl=5 - name of a current block
(i) indicate that velocity reinitialization was done at this step. You will simultaneously see that Ek is more than 2.4
pos[1] is a position of a first monomer
dr is sqrt(mean square displacement) of monomers, i.e. how much did a monomer shift on average.
kin=3.65 pot=3.44 - energies: kinetic, potential
Rg=107.312 - current radius of gyration (size of the system)
SPS - steps per second
Functions depend on each other, and have to be applied in certain groups
load — Mandatory
setup — Mandatory
setLayout — Mandatory, after self.load()
saveFolder — Optional (default is folder with the code)
self.add___Force() — Use any set of forces
Then go all the addBond, and other modifications and tweaks of forces.
Before running actual simulation, it is advised to resolve all possible conflict by doing energyMinimization
doBlock — the actual simulation
save — saves conformation
Select GPU (“0” or “1”) - setup
Select chain/ring - setLayout
Select timestep or collision rate - Simulation
Base class for openmm simulations
Methods
Sets up the important low-level parameters of the platform. Mandatory to run.
| Parameters: | platform : string, optional
PBC : bool, optional
PBCbox : (float,float,float), optional
GPU : “0” or “1”, optional
integrator : “langevin”, “variableLangevin”, “verlet”, “variableVerlet”,
verbose : bool, optional
errorTol : float, optional
|
|---|
sets the folder where to save data.
| Parameters: | folder : string
|
|---|
Sets configuration of the chains in the system. This information is later used by the chain-forming methods, e.g. addHarmonicPolymerBonds() and addStiffness(). This method supersedes the less general getLayout().
| Parameters: | chains: list of tuples :
|
|---|
loads data from file. Accepts text files, joblib files or pure data as Nx3 or 3xN array
If h5dictKey is specified, uses new h5dict-based I/O
| Parameters: | filename : joblib file, or text file name, or Nx3 or 3xN numpy array
center : bool, optional
h5dictKey : int or str, optional
masses : array
|
|---|
Saves conformation plus some metadata. Metadata is not interpreted by this library, and is for your reference
If data is saved to the .vtf format, the same filename should be specified each time. .vtf format is then viewable by VMD.
Initializes an HDF5-based storage for multiple conformation.
When the storage is initialized, save() by default saves to the storage.
If “r+” mode is chosen, simulation is automaticaly set up to continue from existing conformation. In that case, last step is automatically determined, and data from second-to-last file is loaded.
Note
Continue mode does not copy forces and layouts!
| Parameters: | filename : str
mode : :
|
|---|
Sets particle positions
| Parameters: | data : Nx3 array-line
|
|---|
Sets up domains for the simulation. Also, pickles domain vector to “domains.dat”.
| Parameters: | domains : boolean array or None
filename : str or None
|
|---|
Adds bond between two particles, allows to specify parameters
| Parameters: | i,j : int
bondWiggleDistance : float
bondType : “Harmonic” or “Grosberg”
verbose : bool
|
|---|
Adds harmonic bonds connecting polymer chains wiggleDist controls the distance at which energy of the bond equals kT
Adds FENE bonds according to Halverson-Grosberg paper. (Halverson, Jonathan D., et al. “Molecular dynamics simulation study of
nonconcatenated ring polymers in a melt. I. Statics.” The Journal of chemical physics 134 (2011): 204904.)
This method has a repulsive potential build-in, so that Grosberg bonds could be used with truncated potentials. Is of no use unless you really need to simulate Grosberg-type system.
| Parameters: | k : float, optional
|
|---|
Adds harmonic angle bonds. k specifies energy in kT at one radian If k is an array, it has to be of the length N. Xth value then specifies stiffness of the angle centered at monomer number X. Values for ends of the chain will be simply ignored.
| Parameters: | k : float or list of length N
|
|---|
Adds stiffness according to the Grosberg paper. (Halverson, Jonathan D., et al. “Molecular dynamics simulation study of
nonconcatenated ring polymers in a melt. I. Statics.” The Journal of chemical physics 134 (2011): 204904.)
Parameters are synchronized with normal stiffness
If k is an array, it has to be of the length N. Xth value then specifies stiffness of the angle centered at monomer number X. Values for ends of the chain will be simply ignored.
| Parameters: | k : float or N-long list of floats
|
|---|
Adds a special force which could be use for very efficient resolution of crossings Use this force if your monomers are all “on top of each other” E.g. if you start your simulations with fractional brownyan motion with h < 0.4
This is the fastest non-transparent repulsive force. Done according to the paper: (Halverson, Jonathan D., et al. “Molecular dynamics simulation study of
nonconcatenated ring polymers in a melt. I. Statics.” The Journal of chemical physics 134 (2011): 204904.)
This is a simple polynomial repulsive potential. It has the value of trunc at zero, stays flat until 0.6-0.7 and then drops to zero together with its first derivative at r=1.0.
| Parameters: | trunc : float
|
|---|
This is a simple and fast polynomial force that looks like a smoothed version of the square-well potential. The energy equals repulsionEnergy around r=0, stays flat until 0.6-0.7, then drops to zero together with its first derivative at r=1.0. After that it drop down to attractionEnergy and gets back to zero at r=`attractionRadius`.
The energy function is based on polynomials of 12th power. Both the function and its first derivative is continuous everywhere within its domain and they both get to zero at the boundary.
| Parameters: | repulsionEnergy: float :
repulsionRadius: float :
attractionEnergy: float :
attractionEnergy: float :
|
|---|
This is almost the same potential as in addSmoothSquareWellTailedForce. The only difference is that the attractive part of the potential flattens out to the value of tailEnergy at r=`attractionRadius` and then goes quadratically to zero at tailRadius. Please, refer to the documentation for addSmoothSquareWellForce for the details of the repulsive and attractive parts of the potential.
| Parameters: | kwargs: :
tailEnergy: :
tailRadius: :
|
|---|
Adds a lennard-jones force, that allows for mutual attraction. This is the slowest force out of all repulsive.
Note
This is the only force that allows for so-called “exceptions’. Exceptions allow you to change parameters of the force for a specific pair of particles. This can be used to create short-range attraction between pairs of particles. See manual for Openmm.NonbondedForce.addException.
| Parameters: | cutoff : float, optional
domains : bool, optional
epsilonRep : float, optional
epsilonAttr : float, optional
blindFraction : float, 0<x<1
sigmaRep, sigmaAttr: float, optional :
|
|---|
A softened version of lennard-Jones force. Now we’re moving to polynomial forces, so go there instead.
used to exclude a bunch of particles from calculation of nonbonded force
| Parameters: | particles : list
|
|---|
Adds attractive short-range interaction of strength epsilon between particles i,j and a few neighboring particles requires :py:func:’LennardJones Force<Simulation.addLennardJonesForce>’
| Parameters: | i,j : int
epsilon : float
sigma : float, optional
length : int, optional, default = 3
|
|---|
Constrain particles to be within a sphere. With no parameters creates sphere with density .3
| Parameters: | r : float or “density”, optional
k : float, optional
density : float, optional, <1
|
|---|
Excludes particles from a sphere of radius r at certain position.
Attracts one domain to the lamina. Infers radius from spherical confinement, that has to be initialized already.
| Parameters: | width : float, optional
depth : float, optional
r : float, optional
|
|---|
tethers particles in the ‘particles’ array. Increase k to tether them stronger, but watch the system!
| Parameters: | particles : list of ints
k : int, optional
|
|---|
adds force pulling downwards in z direction When using cutoff, acts only when z>cutoff
Initializes particles velocities
| Parameters: | mult : float, optional
|
|---|
Sends particle coordinates to OpenMM system. If system has exploded, this is
used in the code to reset coordinates.
Reinitializes the OpenMM context object. This should be called if low-level parameters, such as forces, have changed.
| Parameters: | mult : float, optional
|
|---|
A wrapper to the build-in OpenMM Local Energy Minimization
Runs system at smaller timestep and higher collision rate to resolve possible conflicts.
Now we’re moving towards local energy minimization, this is here for backwards compatibility.
performs one block of simulations, doing steps timesteps, or steps_per_block if not specified.
| Parameters: | steps : int or None
increment : bool, optional
num : int or None, optional
|
|---|
A subclass used to do simulations for the Metaphase project
Methods
Attracts a subset of particles to the core, repells the rest from the core
Limits position of a set of particles in z coordinate
| Parameters: | particles : list
zCoordinates : list, or tuple of length 2
k : float, optional
useOtherAxis : “x”,”y” or “z”, optional
|
|---|
contains some experimental features
Methods
quickly loads a set of repulsive chains, possibly adds spherical confinement


{% extends 'main.html' %} {% block content %} {% csrf_token %} Are you sure you want to delete "{{object}}"?


Current Progress:
All problems and subproblems are solved with the results being graphed and printed to std.out as necessary.
Below is the video showing the graphs
All problems and subproblems are solved with the results being graphed and printed to std.out as necessary.
Below is the video showing the graphs


Download Code
Background and motivation
An idealized version of a MEMS device consists of two conducting plates connected to an electric circuit
(see Figure 1).
The upper plate is rigid and fixed while the lower one is elastic and fixed only at the boundary.
Initially the plates are parallel and at unit distance from each other.
When a voltage (difference of potential between the two plates) is applied, the lower
plate starts to bend and, if the voltage is large enough,
the lower plate eventually touches the upper one, conducting to the so-called pull-in instability. In the mathematical framework, this phenomenon is known as quenching or touchdown.
Such device can be used for instance as an actuator, a microvalve (the touching-down part closes the valve),
or a fuse.
Figure 1: Two-membrane MEMS device
We consider a well-known model for micro-electromechanical systems (MEMS)
with variable dielectric permittivity, based on the following parabolic equation with singular nonlinearity:
where $\Omega$ is a smoothly bounded domain of $\mathbb{R}^2$ and
is a Hölder continuous function in .
In this mathematical model, the domain $\Omega$ represents the shape of the elastic plate in the horizontal direction, the solution $u=u(t,x)$ measures its vertical deflection,
while the function $f(x)$ is proportional to the constant voltage and characterizes the varying dielectric permittivity of the elastic plate.
We can write the permittivity profile $f$ as follows:
where $\lambda>0$ is the applied voltage, $\varepsilon_0>0$ is the permittivity of the vacuum and $\varepsilon_1(x)$ is the dielectric permittivity of the material.
As a key feature, in our model the permittivity of the elastic plate may be inhomogeneous,
and this can be used to trigger the properties of the device.
We refer to [1],[4],[5] and the references therein for the full details of the model derivation.
It is well known that problem (\ref{quenching problem}) admits a unique maximal classical solution $u$.
We denote its maximal existence time by $T=T_f\in (0,\infty]$. Moreover,
under some largeness assumption on $f$, it is known that the maximum of $u$ reaches the value $1$
at a finite time, so that $u$ ceases to exist in the classical sense. This is what we call touchdown in finite time $T_f<\infty$.
Actually, if we consider $f(x) = \lambda\dfrac{\varepsilon_0}{\varepsilon_1(x)}$,
it is well-known that there exists a positive $\lambda^\ast$, known as pull-in voltage, which depends on $\Omega$ and $\varepsilon_1(x)$, such that
$\bullet \quad $ If $\lambda<\lambda^\ast$, then $T_f=\infty$ and the global classical solution converges to the minimal positive steady state.
$\bullet \quad $ If $\lambda>\lambda^\ast$, then $T_f<\infty$, and then touchdown occurs in finite time.
In the actual design of a MEMS device there are several issues that must be considered.
Typically, one of the design goals is to achieve the maximum possible stable steady-state with relatively small applied voltage $\lambda$. Another consideration may be to increase the stable operating range of the device by increasing the pull-in voltage.
For other devices, such as micropumps and microvalves, where touchdown behavior is explicitly exploited,
it is of interest to be able to localize the touchdown points, or similarly, to be able to avoid touchdown in certain parts of the device.
Our approach to achieve this last goal is to consider a material with varying dielectric permittivity allowing us to localize the touchdown points by a suitable choice of the permittivity profile.
Results
We start by the definition of touchdown point.
A point $x = x_0$ is called a touchdown or quenching point if there exists a sequence ${(x_n , t_n )} \in \Omega\times (0, T)$ such that
The set of all such points is called the touchdown or quenching set, denoted by $\mathcal{T}=\mathcal{T}_f\subset\overline{\Omega}$.
We show in [2] that touchdown can actually be ruled out in subregions of $\Omega$
where $f$ is positive but suitably small, below a positive threshold.
Theorem 1:
Let $\Omega\subset \mathbb{R}^n$ a smooth bounded domain and $f$ a function satisfying
There exists $\gamma_0>0$ depending only on $\Omega,M,\mu,r$ such that:
(i) $\quad$ For any $x_0\in \Omega$, if $f(x_0) <\gamma_0 {\hskip 1pt} \text{dist}^3 (x_0,\partial\Omega)$, then $x_0$ is not a touchdown point.
(ii) $\quad $ For any $\omega\subset\subset \Omega$, if $\displaystyle\sup_{x\in \overline{\Omega}\setminus \omega} f(x) <
\gamma_0 {\hskip 1pt} \text{dist}^3(\omega,\partial\Omega)$, then the touchdown set
is contained in $\omega$.
Roughly speaking, the statement (i) in the above theorem allows one to rule out touchdown in an interior point by choosing a permittivity profile which is sufficiently small at that point, while statement (ii) allows to design devices producing touchdown inside any given subset of $\Omega$ by choosing a permittivity profile concentrated in that subset.
Numerical Simulation 1: no touchdown at the origin
In our first example, we consider a circular elastic plate of radius 1, that is $\Omega = B(0,1)\subset\mathbb{R}^2$.
It is well known that if the dielectric permittivity is constant, the unique touchdown point is the center of the disk.
As consequence of Theorem 1 (i), we can prevent touchdown to occur at the origin by choosing a permittivity profile $f$ such that $f(0)$ is sufficiently small.
Let’s assume that the applied voltage $\lambda$, together with the permittivity of the vacuum $\varepsilon_0$ and the permittivity of the material $\varepsilon_1$ are such that
In this case, we might cover the center of the disk with a material with higher permittivity so that the value of $\varepsilon_1(x)$ in $B(0,1/4)$ is (for example) twice its value in $\Omega\setminus B(0,1/4)$.
That is, we consider the following permittivity profile:
The following video represents the evolution of the elastic plate from the rest position to the pull-in instability.
For the numerical simulation we have applied an implicit Crank-Nicolson scheme in polar coordinates with number of meshpoint $N=100$ in the radial interval $[0,1]$.
Simulation 1: Evolution of the elastic plate until pull-in instability (touchdown). The solution reaches the value 1 in a circumference and then, touchdown is avoided at the center of the plate.
In the schematic video, we remove the upper plate of the MEMS device in order to see the final profile of the solution.
Numerical Simulation 2: touchdown near a prescribed circumference
Let us suppose now that we want our system to touch down in a circumference of radius near $0.7$.
This time we can use Theorem 1 (ii). We will choose a permittivity profile $f$ sufficiently concentrated near a circumference of radius $0.7$. Consider for example:
The following video represents the evolution of the elastic plate from the rest position to the pull-in instability.
In Figure 2 below, we plot the radial final touchdown profile.
For the numerical simulation we have applied an implicit Crank-Nicolson scheme in polar coordinates with number of meshpoint $N=100$ in the radial interval $[0,1]$.
Simulation 2: Evolution of the elastic plate until pull-in instability (touchdown). The solution reaches the value 1 in a circumference of radius near $0.7$.
In the schematic video, we remove the upper plate of the MEMS device in order to see the final profile of the solution.
Figure 2: Plot of the radial touchdown profile. Observe that, as expected, touchdown occurs on a circumference of radius between $0.65$ and $0.75$.
Nontrivial touchdown sets
In view of Theorem 1,
it is a natural question whether such smallness conditions are actually necessary,
or whether touchdown could be shown to occur only at or near the maximum points of the permittivity profile $f$.
In this connection, using stability properties of the touchdown set,
in [2] we construct radial ‘‘M’‘-shaped profiles giving rise to
single-point touchdown at the origin.
Numerical simulation 3:
For this example, we have considered the following radial M-shaped profile in a disk of radius 1:
For this profile, the unique touchdown point is at the origin, far away from the maxima of $f$.
Therefore, if we want to prevent touchdown at the origin, we need to choose a permittivity profile $f$ such that $f(0)$ is small enough (below a certain thershold).
For the numerical simulation we have applied an implicit Crank-Nicolson scheme in polar coordinates with number of meshpoint $N=100$ in the radial interval $[0,1]$.
Simulation 3: Evolution of the elastic plate until pull-in instability (touchdown). Although we consider a ''M''-shaped permittivity profile, the solution touches down only at the origin, far away from the maximum of $f$.
In the schematic video, we remove the upper plate of the MEMS device in order to see the final profile of the solution.
Numerical simulation 4:
Another rather surprising example is the following radially increasing profile:
For this example, the unique touchdown point is the origin, which is actually the global minimum of $f$. In [2], we give a rigorous proof of the existence of this kind of behaviors. It is based on a stability result of the touchdown set combined with the fact that single-point touchdown occurs for constant permittivity profiles.
For the numerical simulation we have applied an implicit Crank-Nicolson scheme in polar coordinates with number of meshpoint $N=100$ in the radial interval $[0,1]$.
Simulation 4: Evolution of the elastic plate until pull-in instability (touchdown). Although the permittivity profile is radially increasing, the unique touchdown point is the origin, the minimum point of $f$.
In the schematic video, we remove the upper plate of the MEMS device in order to see the final profile of the solution.
Quantitative results in 1 dimension
Motivated by practical considerations of MEMS design, our aim in [3] is to further investigate the
touchdown localization problem
and to show that in one space dimension, where analytic computations can be made more precise,
one can obtain quite quantitative conditions.
Namely, we look for a lower estimate of the ratio $\rho$ between $f$ and its maximum,
below which no touchdown occurs on a subregion of $\Omega$.
Rather surprisingly, it turns out that, under suitable assumptions on $f$,
our methods yield values of
the threshold-ratio $\rho$ which are not ‘‘small’’ but can actually be up to the order
which could hence be quite appropriate for robust practical use.
In order to give good estimates of the ratio $\rho$, we shall consider two typical situations, which roughly correspond to a one-bump or a two-bump shape for the profile $f$.
The touchdown is ruled out in a subinterval respectively located between a bump and
an endpoint of $\Omega$, or between two bumps.
The idea behind this is that the plate can be covered with two dielectric materials,
one with a high permittivity and the other with a lower permittivity. We then seek for a ratio between the two permittivities, allowing to rule out touchdown in the low permittivity region.
Reduction to a finite-dimensional optimization problem
As a consequence of our method, the threshold-ratio $\rho$ is rigorously obtained as the solution of a suitable finite-dimensional optimization problem, with either three or four parameters.
An advantage of our results is that they apply to large classes of configurations, so that detailed numerics need not be carried out to localize the touchdown set for particular cases.
For the precise statements of the results, as well as for a detailed study of the optimization problem and numerical estimates of the threshold ratio, we refer the lector to [3].
The Matlab codes to compute numerical estimates of the solution of the optimization problem are availabe at the beginig of the page.
Here we give two concrete examples in order to illustrate
the results.
The threshold ratio is obtained by a simple numerical procedure applied to the finite-dimensional optimization problem.
The following two figures represent some typical permittivity profiles $f(x)$ and the localization of the corresponding touchdown sets
in the one-bump and two-bump cases respectively.
The touchdown sets are localized in a neighborhood of the bumps, represented by the fat lines.
Figure 3: An illustration of the localization of thouchdown set for a one-bump permittivity profile.
Here, the figure represents the permittivity profile $f$ and not the profile of the solution.
Figure 4: An illustration of the localization of thouchdown set for a two-bump permittivity profile.
Here, the figure represents the permittivity profile $f$ and not the profile of the solution.
Numerical simulation 5:
We give an example of a one-bump permittivity profile, similar to the one in Figure 3.
Although our result applies to a large class of profiles, here we consider, for computational simplicity, the following bang-bang profile:
The following video represents the evolution of a 1-dimensional membrane
with a one-bump permittivity profile $f$.
For the numerical simulation we have applied an implicit Crank-Nicolson scheme with number of meshpoint $N=1000$ in the interval $[-6,6]$.
Simulation 5: Evolution of the elastic 1-dimensional membrane until pull-in instability (touchdown). We see that touchdown is localized in the region where $f$ is big (see Figure 3).
Numerical simulation 6:
We give an example of a two-bump permittivity profile, similar to the one in Figure 4.
Although our result applies to a large class of profiles, here we consider, for computational simplicity,
the following bang-bang profile:
The following video represents the evolution of a 1-dimensional membrane
with a two-bump permittivity profile $f$.
For the numerical simulation we have applied an implicit Crank-Nicolson scheme with number of meshpoint $N=1000$ in the interval $[-10,10]$.
Simulation 6: Evolution of the elastic 1-dimensional membrane until pull-in instability (touchdown). We see that touchdown is localized in the region where $f$ is big (see Figure 4).
References
[1] P. Esposito, N. Ghoussoub, Y. Guo, Mathematical analysis of partial differential equations modeling electrostatic MEMS. Courant Lecture Notes in Mathematics, 20. Courant Institute of Mathematical Sciences, New York; American Mathematical Society, Providence, RI, 2010. xiv+318 pp.
[2] C. Esteve, Ph. Souplet, No touchdown at points of small permittivity and nontrivial touchdown sets for the MEMS problem. Advances in Differential Equations, Vol 24, Number 7-8(2019), 465-500.
[3] C. Esteve, Ph. Souplet, Quantitative touchdown localization for the MEMS problem with variable dielectric permittivity. Nonlinearity} 31 4883 (2018).
[4] Ph. Laurençot, Ch. Walker, Some singular equations modeling MEMS. Bull. Amer. Math. Soc. 54 (2017), 437-479.
[5] J.A. Pelesko, D.H. Bernstein, Modeling MEMS and NEMS, Chapman Hall and CRC Press, 2002.


sphinx.ext.autosummary
– Generate autodoc summaries¶
New in version 0.6.
This extension generates function/method/attribute summary lists, similar to those output e.g. by Epydoc and other API doc generation tools. This is especially useful when your docstrings are long and detailed, and putting each one of them on a separate page makes them easier to read.
The sphinx.ext.autosummary
extension does this in two parts:
There is an
autosummary
directive for generating summary listings that contain links to the documented items, and short summary blurbs extracted from their docstrings.Optionally, the convenience script sphinx-autogen or the new :confval:`autosummary_generate` config value can be used to generate short “stub” files for the entries listed in the
autosummary
directives. These files by default contain only the correspondingsphinx.ext.autodoc
directive, but can be customized with templates.
-
.. autosummary::
¶ Insert a table that contains links to documented items, and a short summary blurb (the first sentence of the docstring) for each of them.
The
autosummary
directive can also optionally serve as atoctree
entry for the included items. Optionally, stub.rst
files for these items can also be automatically generated when :confval:`autosummary_generate` is True.For example,
.. currentmodule:: sphinx .. autosummary:: environment.BuildEnvironment util.relative_uri
produces a table like this:
Autosummary preprocesses the docstrings and signatures with the same :event:`autodoc-process-docstring` and :event:`autodoc-process-signature` hooks as
autodoc
.Options
If you want the
autosummary
table to also serve as atoctree
entry, use thetoctree
option, for example:.. autosummary:: :toctree: DIRNAME sphinx.environment.BuildEnvironment sphinx.util.relative_uri
The
toctree
option also signals to the sphinx-autogen script that stub pages should be generated for the entries listed in this directive. The option accepts a directory name as an argument; sphinx-autogen will by default place its output in this directory. If no argument is given, output is placed in the same directory as the file that contains the directive.You can also use
caption
option to give a caption to the toctree.New in version 3.1: caption option added.
If you don’t want the
autosummary
to show function signatures in the listing, include thenosignatures
option:.. autosummary:: :nosignatures: sphinx.environment.BuildEnvironment sphinx.util.relative_uri
You can specify a custom template with the
template
option. For example,.. autosummary:: :template: mytemplate.rst sphinx.environment.BuildEnvironment
would use the template
mytemplate.rst
in your :confval:`templates_path` to generate the pages for all entries listed. See Customizing templates below.New in version 1.0.
You can specify the
recursive
option to generate documents for modules and sub-packages recursively. It defaults to disabled. For example,.. autosummary:: :recursive: sphinx.environment.BuildEnvironment
New in version 3.1.
sphinx-autogen – generate autodoc stub pages¶
The sphinx-autogen script can be used to conveniently generate stub
documentation pages for items included in autosummary
listings.
For example, the command
$ sphinx-autogen -o generated *.rst
will read all autosummary
tables in the *.rst
files that have
the :toctree:
option set, and output corresponding stub pages in directory
generated
for all documented items. The generated pages by default contain
text of the form:
sphinx.util.relative_uri
========================
.. autofunction:: sphinx.util.relative_uri
If the -o
option is not given, the script will place the output files in the
directories specified in the :toctree:
options.
For more information, refer to the sphinx-autogen documentation
Generating stub pages automatically¶
If you do not want to create stub pages with sphinx-autogen, you can also use these config values:
Customizing templates¶
New in version 1.0.
You can customize the stub page templates, in a similar way as the HTML Jinja
templates, see Templating. (TemplateBridge
is not supported.)
Note
If you find yourself spending much time tailoring the stub templates, this may indicate that it’s a better idea to write custom narrative documentation instead.
Autosummary uses the following Jinja template files:
autosummary/base.rst
– fallback templateautosummary/module.rst
– template for modulesautosummary/class.rst
– template for classesautosummary/function.rst
– template for functionsautosummary/attribute.rst
– template for class attributesautosummary/method.rst
– template for class methods
The following variables available in the templates:
-
name
¶ Name of the documented object, excluding the module and class parts.
-
objname
¶ Name of the documented object, excluding the module parts.
-
fullname
¶ Full name of the documented object, including module and class parts.
-
module
¶ Name of the module the documented object belongs to.
-
class
¶ Name of the class the documented object belongs to. Only available for methods and attributes.
-
underline
¶ A string containing
len(full_name) * '='
. Use theunderline
filter instead.
-
members
¶ List containing names of all members of the module or class. Only available for modules and classes.
-
inherited_members
¶ List containing names of all inherited members of class. Only available for classes.
New in version 1.8.0.
-
functions
¶ List containing names of “public” functions in the module. Here, “public” here means that the name does not start with an underscore. Only available for modules.
-
classes
¶ List containing names of “public” classes in the module. Only available for modules.
-
exceptions
¶ List containing names of “public” exceptions in the module. Only available for modules.
-
methods
¶ List containing names of “public” methods in the class. Only available for classes.
-
attributes
¶ List containing names of “public” attributes in the class/module. Only available for classes and modules.
Changed in version 3.1: Attributes of modules are supported.
-
modules
¶ List containing names of “public” modules in the package. Only available for modules that are packages and the
recursive
option is on.New in version 3.1.
Additionally, the following filters are available
-
escape
(s)¶ Escape any special characters in the text to be used in formatting RST contexts. For instance, this prevents asterisks making things bold. This replaces the builtin Jinja escape filter that does html-escaping.
-
underline
(s, line='=') Add a title underline to a piece of text.
For instance, {{ fullname | escape | underline }}
should be used to produce
the title of a page.
Note
You can use the autosummary
directive in the stub pages.
Stub pages are generated also based on these directives.


{% extends "base.html" %} {% block page_info %}
Because we keep the site absolutely free, there are some overhead costs that cannot be covered by the application itself. Hosting, the domain name, and all the other technical magic that keeps this site online and catering to its users doesn't pay for itself, so donations are very welcome. If you enjoy using the site, please consider giving back here.
If you'd like to financially support this project, there are couple ways in which you can do so. First of all, as this project is open-source and freely available on GitHub, you can head over to the GitHub page and sponsor the project there.
You can also donate one-time or in recurring monthly donations below with PayPal. Your donations help keep the site going.
We'll be transparent. The costs are outlined below:
<EMAIL_ADDRESS>we need to pay as well.If you, or an entity, chooses to donate, you will also have your name below and on the repository as a small means of thanks.
{# list of donators #}


Here shows the definitions of the BLE based UUID Definitions.
◆ ATTR_UUID_INVALID
| const uint16_t ATTR_UUID_INVALID[] |
|
extern |
◆ ATTR_UUID_TYPE_CHARACTERISTIC
| const uint16_t ATTR_UUID_TYPE_CHARACTERISTIC[] |
|
extern |
◆ ATTR_UUID_TYPE_CHARC_AGGREGATE_FORMAT
| const uint16_t ATTR_UUID_TYPE_CHARC_AGGREGATE_FORMAT[] |
|
extern |
Characteristic aggregate format UUID.
◆ ATTR_UUID_TYPE_CHARC_EXTENDED_PROPERTIES
| const uint16_t ATTR_UUID_TYPE_CHARC_EXTENDED_PROPERTIES[] |
|
extern |
Characteristic extended properties UUID.
◆ ATTR_UUID_TYPE_CHARC_PRESENTATION_FORMAT
| const uint16_t ATTR_UUID_TYPE_CHARC_PRESENTATION_FORMAT[] |
|
extern |
Characteristic presentation format UUID.
◆ ATTR_UUID_TYPE_CHARC_USER_DESCRIPTION
| const uint16_t ATTR_UUID_TYPE_CHARC_USER_DESCRIPTION[] |
|
extern |
Characteristic user description UUID.
◆ ATTR_UUID_TYPE_CLIENT_CHARC_CONFIGURATION
| const uint16_t ATTR_UUID_TYPE_CLIENT_CHARC_CONFIGURATION[] |
|
extern |
Client characteristic configuration descriptor UUID.
◆ ATTR_UUID_TYPE_EXTERNAL_REPORT_REFERENCE
| const uint16_t ATTR_UUID_TYPE_EXTERNAL_REPORT_REFERENCE[] |
|
extern |
External report reference UUID.
◆ ATTR_UUID_TYPE_INCLUDE
| const uint16_t ATTR_UUID_TYPE_INCLUDE[] |
|
extern |
◆ ATTR_UUID_TYPE_PRIMARY_SERVICE
| const uint16_t ATTR_UUID_TYPE_PRIMARY_SERVICE[] |
|
extern |
◆ ATTR_UUID_TYPE_REPORT_REFERENCE
| const uint16_t ATTR_UUID_TYPE_REPORT_REFERENCE[] |
|
extern |
◆ ATTR_UUID_TYPE_SECONDARY_SERVICE
| const uint16_t ATTR_UUID_TYPE_SECONDARY_SERVICE[] |
|
extern |
◆ ATTR_UUID_TYPE_SERVER_CHARC_CONFIGURATION
| const uint16_t ATTR_UUID_TYPE_SERVER_CHARC_CONFIGURATION[] |
|
extern |
Client characteristic configuration UUID.
◆ ATTR_UUID_TYPE_VALID_RANGE
| const uint16_t ATTR_UUID_TYPE_VALID_RANGE[] |
|
extern |


Introduction Getting the source Optional installation locations Help in bash-menu Using bash-menu Sub-commands Editing Using the title command Examples
dynamide bash-menu is a menu system for bash which keeps lists of
You use the menu to select from these lists. Selecting a directory from a menu changes to that directory. Selecting a command from a command menu executes that command. You can use the menu or the command line to add to, remove from, and edit these lists.
A fancy bash-prompt is also provided, which give you options to display on one line the title, user, host, pwd, and git-status. See Using the title command.
After you install bash-menu and log in, you'll have a custom prompt, and some new commands:
On GitHub, mash on the "Download ZIP" button, and extract to ~/.bash-menu
, or use wget or curl:
cd ~
curl -o master.zip https://codeload.github.com/dynamide/bash-menu/zip/master
unzip master.zip
mv bash-menu-master/ ~/.bash-menu/
Or, checkout bash-menu from GitHub:
cd ~
git clone https://github.com/dynamide/bash-menu.git .bash-menu
or
cd ~
git clone git@github.com:dynamide/bash-menu.git .bash-menu
Then pull in the bash-menu from your bash profile, by sourcing in the bash menu, e.g.
| ~/.bash_profile |
|---|
| source ~/.bash-menu/.bash_profile |
You can source with .
or source
.
All of the shell aliases created by bash-menu are defined in ~/.bash-menu/aliases
(or $DYNAMIDE_MENU/aliases
). Please review these aliases before launching.
The next time you log in, you'll have a custom prompt, and some new commands. Try the main command d
for example.
Here is a sample bash prompt on two lines with current working directory, and git status:
By default, the above check-out will leave you with a new, hidden directory in your home directory, that is, ~/.bash-menu
, or something like /home/laramie/.bash-menu/
. bash-menu knows about this because it sets DYNAMIDE_MENU in ~/.bash-menu/.bash_profile
.
If you checked out to some directory other than ~/.bash-menu
, for example ~/.my-menu/
then you need to do two things to connect bash-menu to your shell.
1) Edit this file, on the line where it sets DYNAMIDE_MENU (by default it is DYNAMIDE_MENU=~/.bash-menu
), so that bash-menu will know where its home directory is.
| ~/.my-menu/.bash_profile |
|---|
| DYNAMIDE_MENU=~/.my-menu |
| ... |
2) Then, in your ~/.bash_profile source in the bash-menu control file we just edited:
| ~/.bash_profile |
|---|
| source ~/.my-menu/.bash_profile |
To see help, run with -h
or h
which will dump out usage.
d -h
To see help on options:
d h options
To see all the options and their alternate spellings, see:
d h aliases
To see the current configuration, see:
d h info
To get started, just type d
at your new prompt. From there you can choose a listed item by typing it's number.
Here is the dynamide bash-menu being used to change to directory 6 on the menu:
Note that it shows you the directory you chose, "/Users/vcrocla/src/dynamide/build/resource_root", and then a quick "ls" of that directory, then it changes to that directory. You can tell because the fancy bash prompt has changed and now shows the current working directory as /Users/vcrocla/src/dynamide/build/resource_root, and the git status in that directory is (master) which means we are on git branch "master" with no pending pulls or pushes.
From a menus such as the directory menu, you can type another menu option. You can type ?
to see the mini-help of sub-commands at this menu.
You can choose options on the command line, and skip the menus. You can also choose some options after you have launched bash-menu and are sitting in a menu, where you are prompted for a choice. If you type a number from the list of choices, you will get that choice. But there are also sub-commands at these menus. These mirror options available on the command line. So you could, for example, launch right into your command menu like this:
d -m
Or, you could launch the directory menu, then change to the command menu with this sequence:
d
m
This represents typing d
at your bash prompt, then typing m
at the choose dir> prompt.
The edit
sub-command is context-sensitive, and will launch your EDITOR or VISUAL editor to let you edit the correct menu.
Here is an actual example:
The sub-commands take an option form: -h
, a single-letter form: h
, and a word form: help
.
Here are all the sub-command options and their equivalents (-c and -s are completely equivalent):
| option | cmd | cmd | context |
|---|---|---|---|
| -a | a | add | directory, command |
| -c | c | connect | directory, command |
| -d | d | list | command, space |
| -e | e | edit | * |
| -h | h | help | * |
| -i | i | info | * |
| -l | l | list | command, space |
| -m | m | menu | directory, space |
| -s | s | space | directory, command |
| -x | x | delete | directory, command |
| -o | o | options | help |
| -a | a | aliases | help |
| -i | i | info | help |
Options or cmd may be used on the command line.
Options or cmd may be used as sub-commands.
Help takes subcommands options
, aliases
, and info
, or their alternate names listed above.  This prompt can show you:
To see all the options, type
title -h
Here is a sample of what setting various options does to your prompt:
In these examples, my user name is "vcrocla", my host is "SFCAML-G2XFD56", which I override with the fake hostname "myhost".
The title (appears at left of the first line) is any placeholder that reminds you of what this shell was for. If you use -w, or -window, the title is also sent to the shell window's title bar.
My directory "~/src/tagonomy" is a git repository, and its git status in that directory is (master) which means we are on git branch "master" with no pending pulls or pushes. My directory "~/src/dynamide" is also a git repository, and also is on branch "master".
You'll also see the numbers of commits ahead/behind if you are not up-to-date. (Thanks to the authors who wrote git-branch-status
, listed in our NOTICE file.)
Here is what it looks like when you are ahead:
If you type git status
you'll see why:
Here is what it looks like when you are ahead and behind:
If you type git status
(I have it aliased to st
) you'll see why:
To customize your prompt, call title
in your ~/.bash_profile after you source in ~/.bash-menu/.bash_profile:
| ~/.bash_profile |
|---|
| source ~/.bash-menu/.bash_profile |
| source ~/.laramie/.bash_profile |
| ~/.laramie/.bash_profile |
|---|
| DYNAMIDE_SPACES_LIST=~/.laramie/spaces.laramie.list |
| title -user -nohost -title Lappy -window |
You can edit your menus in two ways:
vi
or emacs
.For case (2), bash-menu will launch your EDITOR or VISUAL editor on the appropriate file. Just edit, then save normally. Files contain non-blank lines or separators. Separators are three hyphens alone on one line, like this:
/some/directory/on/dirlist
---
/other/dirs
/other/dirs/bin
| Sub-commands: | |
|---|---|
| d x | launches the delete menu for directory lists |
| d x 3 | deletes directory list item 3 |
| d mx | launches the delete menu for commands |
| d mx 3 | deletes command menu item 3 |
| d m x | launches the delete menu for commands, using submenu |
| d ma | add to the command menu, using command-line |
| d m a | add to the command menu, using submenu |
| d e | launch EDITOR for directory lists |
| d m e | launch EDITOR for the command menu |
| d s | launch the space chooser |
Show your directory menu
d
Show your command menu
m
put shell history item 467 (expanded) into your menu
d -ma !467
put a command into your menu using the alias ma
(installed in ~/.bash-menu/aliases)
ma find . -iname '*my-file.*'
chose menu item 2 and execute it
d -m 2
chose menu item 2 and execute it
m 2
put a separator into your menu using the special string ---
ma ---
Add ~/zanzibar (expanded) to your directory list
d -a ~/zanzibar
Add ~/zanzibar (NOT expanded) to your directory list
d -a '~/zanzibar'
Add $JAVA_HOME (NOT expanded) to your directory list
d -a '$JAVA_HOME'
Add $JAVA_HOME (expanded) to your directory list
d -a $JAVA_HOME
Choose directory 2 from your directory list
d 2
Add . (expanded using `pwd`) to your directory list
d -a .
Add foo
in current directory (expanded using pwd
/foo) to your directory list
d -a foo
Add /var/log (full path, unexpanded) to your directory list
d -a /var/log
Add a frequently used Maven (mvn) command to the menu and use the menu to run it. The command is
mvn -DskipTests -o install
and we are adding the whole thing using the ma command.
mvn
is a popular build tool. You can see where it begins to run with the line "[INFO] Scanning for projects...
Re-run that command without looking at the menu, now that you know the number
You could also run the command in your shell, then use the ma
command to capture the command to your command list in your current space. The ma command will take a command-line as its arguments.  Note that you need to read the output of the ma command to see the index of the new command, in this case, the number 4
.
mvn -DskipTests -o install
ma
m 4


list
webcams
Features I'd Like To Add
Webcams
Current Weather
Current Population
Wifi Hotspots?
Cell towers
Flight traffic for current day
Webcams
Choose the webcams you'd like to view:
The University of Tampa Live Webcam
The University of Tampa - Riverfront Live Webcam


Relaxio is designed to allow users to mix and match sounds for reading, relaxing, and focusing. All sound mp3s were sourced via YouTube. The singing bowls mp3 was made available courtesy of the 33bowls monastery.
To send feedback or suggest new sounds, feel free to reach out via Twitter or my personal website. You may also submit a pull request via Github.
Significant contributions to development were made by Matthew Maxwell, mentor at Bloc.io. All logos and icons were designed by Gisele Schaaf.


nips nips2002 nips2002-157 nips2002-157-reference knowledge-graph by maker-knowledge-mining
Source: pdf
Author: Harald Steck, Tommi S. Jaakkola
Abstract: A common objective in learning a model from data is to recover its network structure, while the model parameters are of minor interest. For example, we may wish to recover regulatory networks from high-throughput data sources. In this paper we examine how Bayesian regularization using a product of independent Dirichlet priors over the model parameters affects the learned model structure in a domain with discrete variables. We show that a small scale parameter - often interpreted as
[1] W. Buntine. Theory refinement on Bayesian networks. Conference on Uncertainty in Artificial Intellig ence, pages 52- 60. Morgan Kaufmann, 1991.
[2] G. Cooper and E. Herskovits. A Bayesian method for the induction of probabilistic networks from data. Machine Learning, 9:309- 47, 1992.
[3] A. P. Dawid. Statistical theory. The prequential approach. Journal of the Royal Statistical Society, Series A , 147:277- 305, 1984.
[4] T. S. Ferguson. A Bayesian analysis of some nonparametric problems. Annals of Statistics, 1:209- 30, 1973.
[5] D. Heckerman. A tutorial on learning with Bayesian networks. In M. I. Jordan (Ed.), Learning in Graphical Models, pages 301- 54. Kluwer , 1996.
[6] D. Heckerman, D. Geiger, and D. M. Chickering. Learning Bayesian networks: the combination of knowledge and statistical data. Machine Learning, 20:197243,1995.
[7] R. E . Kass and L. Wasserman. Formal rules for selecting prior distributions: a review and annotated bibliography. Technical Report 583, CMU, 1993.
[8] S. Petrone and A. E. Raftery. A note on the Dirichlet process prior in Bayesian nonparametric inference with partial exchangeability. Technical Report 297, University of Washington, Seattle, 1995.
[9] J. Sethuraman and R. C. Tiwari. Convergence of Dirichlet measures and the interpretation of their parameter. In S. S. Gupta and J. O. Berger (Eds.), Statistical Decision Theory and Related Topics III, pages 305- 15, 1982.
[10] W. Sewell and V. Shah. Social class, parental encouragement, and educational aspirations. American Journal of Sociology, 73:559- 72, 1968.
[11] M. Stone. Cross-validatory choice and assessment of statistical predictions. Journal of the Royal Statistical Society, Series B, 36:111- 47, 1974.
[12] S. G. Walker and B. K. Mallick. A note on the scale parameter of the Dirichlet process. The Canadian Journal of Statistics, 25:473- 9, 1997.


ABOUT US
Immerse yourself in our creative culture
Pursue your passions at California College of the Arts, where diverse practices meet and inspiration is at every turn. With access to the Bay Area's creative communities and thriving industries, you'll take part in exciting collaborations, deepen your practice, and learn from art and design leaders, including our renowned faculty.