---
layout: archive
title: "Research"
permalink: /research/
author_profile: true
---
{% include base_path %}
{% for post in site.research %}
{% include portfolio-1.html %}
{% endfor %}
I am now working on with Prof. Song in Machine Learning Lab at CODA as an Undergraduate Reseach Assistant. We are now doing the VQA problem and the link of VQA is that
https://visualqa.org/
and my supervisor is
Song Le


Pro_Pack : tools : anim_tools¶
ProPack anim_tools module deals with the more generic animation functions, primarily UI wrapping for some of the base rig inetractions setups.
>>> # import statement for the module via the r9pro decompiler
>>> from Red9.pro_pack import r9pro
>>> r9anim_tools = r9pro.r9import('r9anim_tools')
Base Animation Tools with little or no other code benefits other than UI based system calls
Main Classes
AnimCurveFilter ([parent]) |
ProPack replacement for the interactive curve filter |
IK_FK_MatchingUI ([parent]) |
Basic UI for the FK/IK matching used by metaData |
SpaceMatchingUI ([parent]) |
Basic UI for the Parent Space Switching systems in the mRig codebase. |
WristLock_Spaces_UI ([parent]) |
Basic UI for the management of the WristLock AUX Spaces |
Track_locomotion ([mrig]) |
utility class use to create tracking animation on the locomotion ctrl |
-
anim_filter_ui
()¶
-
class
AnimCurveFilter
(parent=None)¶ Bases:
PySide2.QtWidgets.QMainWindow
,Ui_MainWindow
ProPack replacement for the interactive curve filter
-
closeEvent
(event, *args, **kws)¶
-
staticMetaObject
= <PySide2.QtCore.QMetaObject object>¶
-
-
class
IK_FK_MatchingUI
(parent=None)¶ Bases:
PySide2.QtWidgets.QMainWindow
,Ui_MainWindow
Basic UI for the FK/IK matching used by metaData
-
closeEvent
(event, *args, **kws)¶
-
match_fk_ik
(cached_solution=False, *args)¶ switch to IK mode
-
match_ik_fk
(cached_solution=False, *args)¶ switch to FK mode
-
staticMetaObject
= <PySide2.QtCore.QMetaObject object>¶
-
-
class
SpaceMatchingUI
(parent=None)¶ Bases:
PySide2.QtWidgets.QMainWindow
,Ui_MainWindow
Basic UI for the Parent Space Switching systems in the mRig codebase. This UI now expects the nodes selected to have the “parent” enum attr on them which in turn has expanded the scope to all controllers such as the Prop and WristLock ctrls
-
connect_to_systems
(*args, **kws)¶ update the UI feedback
-
switch_ik_space
()¶
-
closeEvent
(event, *args, **kws)¶
-
staticMetaObject
= <PySide2.QtCore.QMetaObject object>¶
-
-
class
WristLock_Spaces_UI
(parent=None)¶ Bases:
PySide2.QtWidgets.QMainWindow
,Ui_MainWindow
Basic UI for the management of the WristLock AUX Spaces
-
set_mrig
()¶ connect to the rig
-
set_space
(side, aux_slot, newspace=None, align_mode='verbose')¶ set the aux_space for the wristlock and deal with transform changes
Parameters: - side – side of the Arm systems we’re dealing with (‘L’ or ‘R’)
- aux_slot – which aux_slot are we modifying here
- newspace – if given this is the new object we’re binding too, else we use the first selected object
- align_mode – how do we initially align the systems to the new object. * verbose - throws a ConfirmDialog to let you choose * snap_to_new - snaps the wristlock to the pivot of the new object * maintain_wrist - maintains the current wrists transforms * maintain_wristlock - maintains the current wristlock transforms * no_align - does no alignment
-
modify_space
(side, aux_slot, btn)¶
-
select_locks
(side)¶
-
delete_space
(side, slot, verbose=False)¶
-
bake_down
()¶ bake the selected mSytsm wristlocks back to the wrist controller
-
bake_space_to_wrist
(wrist, aux_obj=None, aux_slot=None, time=False, timerange=(), step=1, smartbake=False, smartbake_ref=[])¶ bake the selected mSystem auxSpace object back to the wrist controller, auxSpace object gets the keys
Parameters: - wrist – wrist we’re baking too
- aux_obj – the AuxSpace base object that will track the wrist, maintaining current offset
- aux_slot – allows us to just pass in the aux_slot rather than the connected object
- time – do we drop keys or not?
- timerange – range to process over
- step – frame step between keys if time=True
- smartbake – if True we look at the mSystem’s current keys and only match over those keys if time enabled
- smartbake_ref – smartbake=True if given, used as reference nodes to extract keytimes from, else we look at all nodes about to be processed which isn’t always what we want. If we still find no keytimes we revert to base range times with step given
-
rebuild_wrist_locks
(wristlock_data)¶ from an mrig.gatherInfo block generated within r9Anim.indoDict data, rebuild, or attempt to rebuild the wristlock networks. Used by the r9Anim code for data integrity
-
staticMetaObject
= <PySide2.QtCore.QMetaObject object>¶
-
-
class
HIK_Tpose_to_FBX
(files=None, parent=None, logger=None)¶ Bases:
PySide2.QtWidgets.QMainWindow
,Ui_MainWindow
Simple UI that matches the main pro_to_bnd but just manages the Add HIK from tpose flags. The run func is run by the Browser to allow for bulk processing of FBX files
-
pull_settings
()¶ push the settings back to the UI
-
set_tpose
()¶ set the new TPose management filepath
-
run
()¶ batch run the fbx files, adding HIK definition from the given TPose data
-
staticMetaObject
= <PySide2.QtCore.QMetaObject object>¶
-
-
class
Track_locomotion
(mrig=None)¶ Bases:
object
utility class use to create tracking animation on the locomotion ctrl
Note
By default this is looking for the COG in the mRig structures, however we recently added a by-pass to this. If you connect any node to a message wire called mrig.locomotion_track_pnt then that will by-pass the search for the COG and use that as the Locomotion track pnt instead.
>>> mrig = r9Meta.getMetaRigs()[0] >>> mrig.addAttr('locomotion_track_pnt', attrType='messageSimple', value='locator1') >>> >>> # OR add the attr then use the connection handling to plug it >>> mrig.addAttr('locomotion_track_pnt', attrType='messageSimple') >>> mrig.locomotion_track_pnt = 'locator1'
-
mrig
¶
-
locomotion_ctrl
¶
-
cog_ctrl
¶
-
set_timeranges
()¶
-
delete_locmotion_animation
(attributes=[])¶ delete animation on locomotion ctrl if attributes are pass it will delete just given attributes if no attributes given, all animation will be deleted
Parameters: attributes – list of attributes to be deleted
-
track_to_cog
(translates=True, rotates=True)¶ track COG ctrl animation to the locomotion ctrl
-
project_cog_translation
()¶ projects the COG translations to the ground plane and extracts the directional vector for the rotates
-
project_cog_translation_rotation
()¶ projects COG translations and rotation to locomotion ctrl maintaining locomotion ctrl in the ground
-
linear_translation
()¶ create a linear translation animation on locomotion ctrl
-
track_cog_ty
()¶ create locomotion ctrl animation, tracking just translation Y (or current UpAxis) of COG ctrl
-
track_cog_maintaining_offset
()¶ create locomotion ctrl animation, tracking COG but maintaining the current offset between COG and locomotion ctrl
-
static
()¶ simple projected extraction without any key management and on the current frame only
-


| Data Forms |
XEP-0004 |
n/a |
Allows to gather data using Forms. |
| Last Activity |
XEP-0012 |
n/a |
Communicating information about the last activity associated with an XMPP entity. |
| Flexible Offline Message Retrieval |
XEP-0013 |
n/a |
Extension for flexible, POP3-like handling of offline messages. |
| Privacy Lists |
XEP-0016 |
n/a |
Enabling or disabling communication with other entities. |
| Service Discovery |
XEP-0030 |
n/a |
Allows to discover services in XMPP entities. |
| Extended Stanza Addressing |
XEP-0033 |
n/a |
Allows to include headers in stanzas in order to specifiy multiple recipients or sub-addresses. |
| Multi User Chat |
XEP-0045 |
n/a |
Allows configuration of, participation in, and administration of individual text-based conference rooms. |
| In-Band Bytestreams |
XEP-0047 |
n/a |
Enables any two entities to establish a one-to-one bytestream between themselves using plain XMPP. |
| Bookmarks |
XEP-0048 |
n/a |
Bookmarks, for e.g. MUC and web pages. |
| Private Data |
XEP-0049 |
n/a |
Manages private data. |
| Ad-Hoc Commands |
XEP-0050 |
n/a |
Advertising and executing application-specific commands. |
| vcard-temp |
XEP-0054 |
n/a |
The vCard-XML format currently in use. |
| Jabber Search |
XEP-0055 |
n/a |
Search information repositories on the XMPP network. |
| Result Set Management |
XEP-0059 |
n/a |
Page through and otherwise manage the receipt of large result sets |
| PubSub |
XEP-0060 |
n/a |
Generic publish and subscribe functionality. |
| SOCKS5 Bytestreams |
XEP-0065 |
n/a |
Out-of-band bytestream between any two XMPP entities. |
| XHTML-IM |
XEP-0071 |
n/a |
Allows send and receiving formatted messages using XHTML. |
| In-Band Registration |
XEP-0077 |
n/a |
In-band registration with XMPP services. |
| Advanced Message Processing |
XEP-0079 |
n/a |
Enables entities to request, and servers to perform, advanced processing of XMPP message stanzas. |
| User Location |
XEP-0080 |
n/a |
Enabled communicating information about the current geographical or physical location of an entity. |
| XMPP Date Time Profiles |
XEP-0082 |
n/a |
Standardization of Date and Time representation in XMPP. |
| Chat State Notifications |
XEP-0085 |
n/a |
Communicating the status of a user in a chat session. |
| Time Exchange |
XEP-0090 |
n/a |
Allows local time information to be shared between users. |
| Software Version |
XEP-0092 |
n/a |
Retrieve and announce the software application of an XMPP entity. |
| Stream Initation |
XEP-0095 |
n/a |
Initiating a data stream between any two XMPP entities. |
| SI File Transfer |
XEP-0096 |
n/a |
Transfer files between two users over XMPP. |
| Entity Capabilities |
XEP-0115 |
n/a |
Broadcasting and dynamic discovery of entity capabilities. |
| Jingle |
XEP-0116 |
n/a |
Initiate and manage sessions between two XMPP entities. |
| Data Forms Validation |
XEP-0122 |
n/a |
Enables an application to specify additional validation guidelines . |
| Service Administration |
XEP-0133 |
n/a |
Recommended best practices for service-level administration of servers and components using Ad-Hoc Commands. |
| Stream Compression |
XEP-0138 |
n/a |
Support for optional compression of the XMPP stream. |
| Data Forms Layout |
XEP-0141 |
n/a |
Enables an application to specify form layouts. |
| Personal Eventing Protocol |
XEP-0163 |
n/a |
Using the XMPP publish-subscribe protocol to broadcast state change events associated with an XMPP account. |
| Message Delivery Receipts |
XEP-0184 |
n/a |
Extension for message delivery receipts. The sender can request notification that the message has been delivered. |
| Blocking Command |
XEP-0191 |
n/a |
Communications blocking that is intended to be simpler than privacy lists (XEP-0016). |
| XMPP Ping |
XEP-0199 |
n/a |
Sending application-level pings over XML streams. |
| Entity Time |
XEP-0202 |
n/a |
Allows entities to communicate their local time |
| Delayed Delivery |
XEP-0203 |
n/a |
Extension for communicating the fact that an XML stanza has been delivered with a delay. |
| XMPP Over BOSH |
XEP-0206 |
n/a |
Use Bidirectional-streams Over Synchronous HTTP (BOSH) to transport XMPP stanzas. |
| Attention |
XEP-0224 |
n/a |
Getting attention of another user. |
| Bits of Binary |
XEP-0231 |
n/a |
Including or referring to small bits of binary data in an XML stanza. |
| Best Practices for Resource Locking |
XEP-0296 |
n/a |
Specifies best practices to be followed by Jabber/XMPP clients about when to lock into, and unlock away from, resources. |
| Last Message Correction |
XEP-0308 |
n/a |
Provides a method for indicating that a message is a correction of the last sent message. |
| Last User Interaction in Presence |
XEP-0319 |
n/a |
Communicate time of last user interaction via XMPP presence notifications. |
| Group Chat Invitations |
n/a |
n/a |
Send invitations to other users to join a group chat room. |
| Jive Properties |
n/a |
n/a |
TODO |


---
layout: page
title: "About"
description: "A little about me."
header-img: "img/about-bg.jpg"
---
I’m currently a machine learning research engineer convert coming from a systems engineering background and working on applying machine learning in interesting ways to distributed systems, software and technology infrastructure. I hope to share what I learn along the way here!
Thanks for reading!


Money Play. How should Red play 53?
pips Red=150 White=54
(CorrectAnswer= 0/0, ErrorScore= 0)
I had this position at the Battersea chouette and fairly quickly played 20/15*, 8/5 maximising covers for the 4-pt but it turns out that 20/15*/12 is better.
It provides some indirect covers for the 4-pt and crucially provides extra outfield coverage as well as the bar point may become important. 8/5 takes a checker that may belong on the bar-point to the wrong place.
I was surprised that 20/15*, 8/5 is ranked as a 0.060 error by XG so I found the position very educational.
It provides some indirect covers for the 4-pt and crucially provides extra outfield coverage as well as the bar point may become important. 8/5 takes a checker that may belong on the bar-point to the wrong place.
I was surprised that 20/15*, 8/5 is ranked as a 0.060 error by XG so I found the position very educational.
1. Cubeful 2-ply 20/15*/12 Eq.: +0.149 0.599 0.000 0.000 - 0.401 0.228 0.025 2. Cubeful 2-ply 20/15* 8/5 Eq.: +0.112 (-0.037) 0.583 0.000 0.000 - 0.417 0.228 0.025 3. Cubeful 2-ply 20/15* 13/10 Eq.: +0.101 (-0.048) 0.590 0.000 0.000 - 0.410 0.243 0.036 4. Cubeful 0-ply 20/15* 4/1 Eq.: -0.069 (-0.218) 0.513 0.000 0.000 - 0.487 0.246 0.023 5. Cubeful 0-ply 20/15* 6/3 Eq.: -0.612 (-0.761) 0.368 0.000 0.000 - 0.632 0.415 0.059


Duration
5 minutes
Lab goals
The goal of the exercise is to add the SQLite.NET component to each project in your solution using Nuget.
Required assets
The provided Resources folder for this exercise contains a subfolder named Lab.Completed with a solution you can use to check your work. This lab is a continuation of the previous one. If you did not complete the previous exercise, you can use the Lab.Completed solution from the previous part as starter code for this part.
Exercise challenge
Follow the above goals to complete the exercise. You can refer to the step-by-step instructions below to get more detailed information on each goal.
Steps
Add the SQLite.Net PCL Nuget package
Let's add the Nuget package which will allow us to use SQLite-Net. Make sure you add the correct package - the id is sqlite-net pcl, there are other packages with very similar names so check the entry carefully before you install it!
- If you are using Visual Studio for Mac, right-click the Packages folder in the People Portable Class Library project and select Add Packages... from the popup menu.
- In the Search field, enter sqlite-net pcl.
- Select SQLite-net PCL from the list of search results and then press the Add Package button in the lower right.
- If you are using Visual Studio on Windows, right-click on the People Portable Class Library project name within Solution Explorer, select Manage Nuget Packages....
-
Select the Browse tab and enter
sqlite-net pcl
in the Search field. - Select sqlite-net-pcl in the list of search results and press the Install button.
- Repeat the steps to add the SQLite.NET PCL nuget package for the other projects (iOS, Android, and Windows).
Summary
In this lab, you added SQLite.Net support to each project by adding the SQLite.Net PCL Nuget package. You're now ready to work with a SQLite database.


Importance
Specificity
Order
!Important should only be used as a last resort, or for testing
Later declarations in the document will overwrite earlier ones (read from top to bottom)
Specificity is the measure of how specific a selector is – meaning how many elements it could match
The amount of specificity a selector has is measured using 4 different values which can be thought of as 1000’s 100’s 10’s and 1’s – 4 single digits in 4 columns
So for example:
/* specificity 0113 */
#outer div ul .nav a { }
CSS provides four special universal properties for specifying inheritance
inherit
Sets the property value to a selected element to be the same as that of its parent element
initial
Sets the property value to a selected element to be the same as the value set for that element in the browser’s default style sheet (if no value set by browsers default style sheet and the property is naturally inherited then the property value is set to inherit instead)
unset
Resets the property to its natural value which means if the property is naturally inherited it acts like inherit, otherwise it acts like initial
revert
Reverts the property to the value it would have had if the current origin had not applied any styles to it
Unsurprisingly initial and unset are unsupported in IE


Small PHP mini-website to convert plain text files (.txt and .md) to .xhtml files that can be easily added to EPUB creation software like Calibre-editor or Sigil.
(All images will be referenced in result *.xhtml to "../Images/" for EPUB3 compatibility)


Our first review was quite popular and the feedback we received has been wonderful! We want to thank everyone for their support and take a moment to congratulate our raffle winners.
As part of our review series we hope to release at least one review per month. Along with these reviews, we’re hoping to be able to offer additional discounts and giveaways.
For the next part of this series, we are reviewing Functional Web Development with Elixir, OTP, and Phoenix by Lance Halvorsen.
Author
Lance has been developing software for the web professionally for two decades. He’s worked with a number of languages, frameworks, and approaches during that time. All of those experiences feed into his current thoughts on web development, which are captured in this book.
Lance is also the original author of the Phoenix Guides, and is a Phoenix core team alumnus.
If you want to have an idea about the author and the content of the book, check out this awesome video
Target
What is the target audience of the book? There is no better place to look than the book’s introduction:
On a practical level, this book is for people who have some familiarity with Elixir and Phoenix, and who want to take that knowledge further. But there’s a wider list for whom the ideas in this book will resonate.
For people who view OTP with a little trepidation, or for those who haven’t quite mastered OTP Behaviours, this book will give you the confidence to use OTP in any application.
For people who have felt the sting of tight coupling between business logic and web frameworks, this book will show you a way out of that pain forever. For people who feel constrained by traditional web development, you will learn new techniques and new ways to structure apps that will spark your imagination.
For people who are wondering what all the fuss is about with Elixir and Phoenix, you’ll get a great taste of what makes people so excited. You just might become a convert!
This book is certainly not for beginners and Lance doesn’t mince words when saying as much:
Readers looking for an introduction to Elixir or Phoenix would do well to begin with other resources.
We won’t cover the basics of Elixir. I’ll assume you know them before you begin.
If you need to get up to speed first, don’t worry—we’ll be here when you’re ready. In the meantime, Dave Thomas’s book, Programming Elixir 1.3 [Tho16], is a great place to start.
The same is true for Phoenix. We will take a close look at channels and Presence, but you won’t learn the rest of Phoenix here. You should be able to follow along in this book without that information, but if you want to fill in the gaps, Programming Phoenix [TV16] by Chris McCord, Bruce Tate, and José Valim is the book to reach for.
Review
This book is quite small at only 214 pages, a tutorial covering the development of a game from the beginning to the end, explaining step by step what we are doing and the technology included.
The focus of the book on building a game had me quite interested so I purchased it while still in early beta. This is a standard 2-player position guessing game called Islands (it looks like Battleship). Each player sets up a handful of islands on their boards, and then starts guessing on the opponent island coordinates. When all islands are found, the game ends.
If you took the time to watch the author’s video above, you have an idea of what to expect in the book. Something that might surprise many readers: Phoenix is not your application, it’s simply a presentation layer for our underlying logic. In this book Lance attempts to help readers understand how to properly develop an application from the ground up starting with our business logic and growing from there. Data persistance and UI are details that come later, as they become necessary to support features.
The content is quite nicely paced which makes understanding the topics easy and enjoyable.
Chapter Analysis
The book has 7 chapters divided into 3 main parts: our business logic, implementing OTP behaviours, and finally adding a UI.
Chapter 1 is an introduction, a roadmap of the adventure that lies ahead of us.
In Part 1 we focus on the business logic as a game engine. We begin designing the entities of our game in Chapter 2 and add a custom State Machine to handle our game rules in Chapter 3.
It goes without saying that the first part is the most important one in the book.
Lance seeks to force us to rewire our brains on how to kick start an app, without the use of a framework or the database strangling us from the get-go.
This is the red pill, our way out of the complacency that mix phx.new
and other frameworks have lulled us into.
In the second part of the book we add some important OTP behaviours in our system, a GenServer in Chapter 4 and a Supervision Tree in Chapter 5.
In the final part we introduce our presentation layer: a web-based UI. Here we’ll create a new Phoenix application and add our game engine as a dependency in Chapter 6. In Chapter 7 we explore Channels and Presence to finish implementing our working game.
The structure of the book is based on scalable knowledge, you begin with nothing in your hands, just a miniature elixir app, and start designing around your needs, piece by piece. Not a single chapter feels forced, that it is there just to add some pages or just to introduce something the author wanted to say.
Conclusion
I thoroughly enjoyed the book and my view of our craft in general changed a lot because of it. I started looking for ways to implement this way of programming in other languages / frameworks (mostly in vain, but what can you do?). The design technique described in this book can be applied to every app you can imagine, and it actually makes it easier to build it, because you stop thinking about your app in detail-land (UI, database). It also leads to more maintainable code, as your logic being outside the framework, helps you work on the core of your app and the interface independently, without changes on one having side effects on the other that easily.
That said there are two things that I think would have made it a grand slam: testing and the presentation implementation.
The use of testing, would have been a welcomed addition. Relying on iex
to execute and valuate the code felt time consuming and didn’t drive home the best practices the book encourages elsewhere. While I understand the author’s goal with using iex
I am not entirely sold on this idea. I think an opportunity to demonstrate how to properly test our code was lost. There was a talk with the author in the Pragmatic Bookshelf at the time of development of the book and when asked about this, he responded that he did start working on the book using tests, but the tests started taking over the book.
The second improvement would be on how we implement our presentation layer for two reasons:
Firstly, as with iex
testing above I did not care for relying on the in-browser console to execute and test my JavaScript code.
Through the course of the final section we write a significant amount of JavaScript.
When we go to test our game in another browser, we have to code this JavaScript and run it again via our console.
Correctly building and testing JavaScript applications isn’t the focus on this book but I feel there could have been a better approach.
Finally, the book ends when you are supposed to start building the UI, and provides us with some files to copy paste inside our existing codebase so we can see the final result. We’ve spent over 180 pages understanding why we’re doing what we are and it ends unceremoniously with us copying the majority of our front end code from elsewhere. I know that this book is about Elixir and OTP mostly but in my opinion the author could have written a final part that relied on writing down some code and explaining more along the way. It would have resulted an additional chapter or two but would have provided better closure to those who need it (like myself) while allowing others to skip it. Having said that, I feel I can justify the authors choice on this, as our community’s attitude towards JS tends to be aggressive, but this is a theme for another post.
Giveaway
We are giving away 3 free physical copies of Lance Halvorsen’s Functional Web Development with Elixir, OTP, and Phoenix. Want your chance to win a free copy? Follow us on Twitter and retweet this blog post announcement! We’ll be picking winners on September 15th, don’t miss your chance!
Look for more reviews to come soon!
Caught a mistake or want to contribute to the article? Edit this page on GitHub!


Texas parole board says inmate Rodney Reed's execution should be delayed; governor to make decision
by EndPlayHOUSTON - HOUSTON (AP) - Texas parole board says inmate Rodney Reed's execution should be delayed; governor to make decision.
HOUSTON - HOUSTON (AP) - Texas parole board says inmate Rodney Reed's execution should be delayed; governor to make decision.


%inherit<EMAIL_ADDRESS>/> <%block name="title">BrocadeFW%block>
BrocadeFW is lightweight web application framework written in Python.


REGISTER
Error! Your username may be already taken.
Error! Your password doesn't match password confirmation.
Enjoy instant meals at home...


Half a Billion Dollars in Bitcoin (BTC) Suddenly on the Move As Leading Crypto Consolidates at $8,800
by Daily Hodl StaffBitcoin whales are on the move as the price of the leading cryptocurrency consolidates around $8,800.
In the last 24 hours, some of the biggest Bitcoin holders on the ledger moved 57,421 BTC worth about $502.6 million.
Most of the BTC was moved between wallets of unknown origin. One of the transfers sent 1,487 BTC to the crypto exchange OKEx, indicating a trader may be looking to sell some of their funds on the open market.
Here’s a look at seven of the largest transfers in the last day, totaling 41,367 BTC worth $362.6 million.
- 9,757 BTC worth $85.6 million transferred from unknown wallet to unknown wallet
- 9,866 BTC worth $86.5 million transferred from unknown wallet to unknown wallet
- 2,600 BTC worth $22.6 million transferred from Coincheck to unknown wallet
- 1,600 BTC worth $13.9 million transferred from Coincheck to unknown wallet
- 9,974 BTC worth $87.4 million transferred from unknown wallet to unknown wallet
- 6,083 BTC worth $53.5 million transferred from unknown wallet to unknown wallet
- 1,487 BTC worth $13.1 million transferred from unknown wallet to OKEx
In addition, the crypto custody giant Xapo, which was recently acquired by Coinbase, has been identified by Whale Alert as the entity behind four massive transactions.
The company, which holds huge amounts of crypto in cold storage for institutional clients, moved 16,054 BTC worth $140.0 million.


Files CCore/inc/DynObject.h CCore/src/DynObject.cpp
DynObject is a smart pointer with exclusive ownership and constant propagation. It can be used to create an object dynamically. The object is destroyed when the pointer gets out of the scope.
New()/Delete() with the DefaultHeapAlloc are used to create and destroy the object. So you don't have to derive the object type from the MemBase. Any type can be used, the only assumption is that the object destructor is nothrow.
template <NothrowDtorType T>
class DynObject
{
T *ptr;
public:
// constructors
DynObject() noexcept : ptr(0) {}
explicit DynObject(NothingType) : ptr(New<T>(DefaultHeapAlloc())) {}
template <class ... SS>
explicit DynObject(SS && ... ss) : ptr(New<T>(DefaultHeapAlloc(), std::forward<SS>(ss)... )) {}
~DynObject();
Default constructor creates the null pointer. It points to no object.
NothingType-constructor creates the pointer to the object, constructed using it's default constructor.
// no copy DynObject(const DynObject<T> &obj) = delete ; DynObject<T> & operator = (const DynObject<T> &obj) = delete ; // moving DynObject(DynObject<T> &&obj); DynObject<T> & operator = (DynObject<T> &&obj);
DynObject is not copyable, but movable using the C++ move.
// methods void create(NothingType); template <class ... SS> void create(SS && ... ss); void destroy();
For an existing pointer you can recreate the object using the method create() (the previous object, if any, is destroyed) or destroy it using the method destroy(). The method destroy() sets the pointer to the null state. The method create() preserves the pointer state, if the object creation ends with the throwing of an exception.
// object pointer, const enforcement const T * operator + () const { return ptr; } bool operator ! () const { return !ptr; } T * getPtr() { return ptr; } const T * getPtr() const { return ptr; } const T * getPtr_const() const { return ptr; } T & operator * () { return *ptr; } const T & operator * () const { return *ptr; } T * operator -> () { return ptr; } const T * operator -> () const { return ptr; }
The usual set of methods can be used to access the object. The difference with the Object Pointer Interface is that the constantness is propagated from the pointer to the object.
// object swap/move void objSwap(DynObject<T> &obj); explicit DynObject(ToMoveCtor<DynObject<T> > obj); DynObject<T> * objMove(Place<void> place); };
DynObject is swappable and CCore-movable.


{% extends "layout.html" %} {% block page_title %} GOV.UK prototyping kit {% endblock %} {% block propositionHeader %} {% include "includes/propositional_navigation.html" %} {% endblock %} {% block content %} {% include "includes/left_nav_settings.html" %} Settings - amend user Change location Amend user Delete record Standards Confirmation You are about to change a user from Alice to Bob or You are about to remove Alice from the workcoach list Are you sure you want to do this? Yes No {% endblock %}
Confirmation
You are about to change a user from Alice to Bob
or
You are about to remove Alice from the workcoach list
Are you sure you want to do this?


Amber2Gromos Example¶
[1]:
from pygromos.files.forcefield import _generic_force_field
from pygromos.files.gromos_system import gromos_system
from pygromos.files.forcefield.amber import amberff
from pygromos.gromos.gromosPP import _gromosPPbase
[2]:
# note: ambertools is required. you can install it eg with: conda install -c conda-forge ambertools
ff = amberff.AmberFF(name = "amberff_gaff")
[3]:
molecule = "example_files/amber2gromos/aniline.mol2"
[11]:
gromosPP_bin_dir = None #ADAPT HERE
create top + cnf for aniline¶
[12]:
ff.solvate = False
system = gromos_system.Gromos_System(work_folder = "example_files/amber2gromos",
system_name = "aniline",
forcefield = ff,
auto_convert = True,
in_mol2_file = molecule,
in_gromosPP_bin_dir = gromosPP_bin_dir)
['/home/salome/pymol/envs/pygromosx/bin/antechamber', '-i', '/home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.mol2', '-fi', 'mol2', '-o', 'aniline.mol2', '-fo', 'mol2', '-s', '2', '-c', 'bcc', '-nc', '0']
Welcome to antechamber 21.0: molecular input file processor.
acdoctor mode is on: check and diagnose problems in the input file.
The atom type is set to gaff; the options available to the -at flag are
gaff, gaff2, amber, bcc, and sybyl.
-- Check Format for mol2 File --
Status: pass
Info: Ignoring Mol2 record type (@<TRIPOS>SUBSTRUCTURE).
Info: Finished reading file (/home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.mol2); atoms read (14), bonds read (14).
Info: Determining atomic numbers from atomic symbols which are case sensitive.
-- Check Unusual Elements --
Status: pass
-- Check Open Valences --
Status: pass
-- Check Geometry --
for those bonded
for those not bonded
Status: pass
-- Check Weird Bonds --
Status: pass
-- Check Number of Units --
Status: pass
acdoctor mode has completed checking the input file.
Running: /home/salome/pymol/envs/pygromosx/bin/bondtype -j full -i ANTECHAMBER_BOND_TYPE.AC0 -o ANTECHAMBER_BOND_TYPE.AC -f ac
Running: /home/salome/pymol/envs/pygromosx/bin/atomtype -i ANTECHAMBER_AC.AC0 -o ANTECHAMBER_AC.AC -p gaff
Info: Total number of electrons: 50; net charge: 0
Running: /home/salome/pymol/envs/pygromosx/bin/sqm -O -i sqm.in -o sqm.out
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
Running: /home/salome/pymol/envs/pygromosx/bin/am1bcc -i ANTECHAMBER_AM1BCC_PRE.AC -o ANTECHAMBER_AM1BCC.AC -f ac -p /home/salome/pymol/envs/pygromosx/dat/antechamber/BCCPARM.DAT -s 2 -j 1
Running: /home/salome/pymol/envs/pygromosx/bin/atomtype -f ac -p bcc -o ANTECHAMBER_AM1BCC.AC -i ANTECHAMBER_AM1BCC_PRE.AC
['/home/salome/pymol/envs/pygromosx/bin/parmchk2', '-i', '/home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/antechamber_tmp/aniline.mol2', '-f', 'mol2', '-o', 'aniline.frcmod']
['/home/salome/pymol/envs/pygromosx/bin/tleap', '-f', 'aniline.cmd']
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/prep to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/lib to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/parm to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/cmd to search path.
-f: Source aniline.cmd.
Welcome to LEaP!
(no leaprc in search path)
Sourcing: ./aniline.cmd
----- Source: /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.gaff
----- Source of /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.gaff done
Log file: ./leap.log
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/gaff.dat
Reading title:
AMBER General Force Field for organic molecules (Version 1.81, May 2017)
----- Source: /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.water.tip3p
----- Source of /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.water.tip3p done
Loading library: /home/salome/pymol/envs/pygromosx/dat/leap/lib/atomic_ions.lib
Loading library: /home/salome/pymol/envs/pygromosx/dat/leap/lib/solvents.lib
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.tip3p
Reading force field modification type file (frcmod)
Reading title:
This is the additional/replacement parameter set for TIP3P water
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ions1lm_126_tip3p
Reading force field modification type file (frcmod)
Reading title:
Li/Merz ion parameters of monovalent ions for TIP3P water model (12-6 normal usage set)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ionsjc_tip3p
Reading force field modification type file (frcmod)
Reading title:
Monovalent ion parameters for Ewald and TIP3P water from Joung & Cheatham JPCB (2008)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ions234lm_126_tip3p
Reading force field modification type file (frcmod)
Reading title:
Li/Merz ion parameters of divalent to tetravalent ions for TIP3P water model (12-6 normal usage set)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.chcl3
Reading force field modification type file (frcmod)
Reading title:
chloroform frcmod file
Using modified Bondi radii
Loading parameters: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/parmchk_tmp/aniline.frcmod
Reading force field modification type file (frcmod)
Reading title:
Remark line goes here
Loading Mol2 file: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/antechamber_tmp/aniline.mol2
Reading MOLECULE named ligand_1
Checking Unit.
Building topology.
Building atom parameters.
Building bond parameters.
Building angle parameters.
Building proper torsion parameters.
Building improper torsion parameters.
total 7 improper torsions applied
Building H-Bond parameters.
Incorporating Non-Bonded adjustments.
Not Marking per-residue atom chain types.
Marking per-residue atom chain types.
(Residues lacking connect0/connect1 -
these don't have chain types marked:
res total affected
LI1 1
)
(no restraints)
Writing pdb file: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/tleap_tmp/aniline.leap.pdb
Quit
Exiting LEaP: Errors = 0; Warnings = 0; Notes = 0.
converted topology saved to /home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.top
converted coordinates saved to /home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.cnf
create top + cnf for aniline, solvated in CHCl3¶
[6]:
ff.solvate = True
ff.solventbox = "CHCL3BOX"
[7]:
system = gromos_system.Gromos_System(work_folder = "example_files/amber2gromos",
system_name = "aniline",
forcefield = ff,
auto_convert = True,
in_mol2_file = molecule,
in_gromosPP_bin_dir = gromosPP_bin_dir)
['/home/salome/pymol/envs/pygromosx/bin/antechamber', '-i', '/home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.mol2', '-fi', 'mol2', '-o', 'aniline.mol2', '-fo', 'mol2', '-s', '2', '-c', 'bcc', '-nc', '0']
Welcome to antechamber 21.0: molecular input file processor.
acdoctor mode is on: check and diagnose problems in the input file.
The atom type is set to gaff; the options available to the -at flag are
gaff, gaff2, amber, bcc, and sybyl.
-- Check Format for mol2 File --
Status: pass
Info: Ignoring Mol2 record type (@<TRIPOS>SUBSTRUCTURE).
Info: Finished reading file (/home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.mol2); atoms read (14), bonds read (14).
Info: Determining atomic numbers from atomic symbols which are case sensitive.
-- Check Unusual Elements --
Status: pass
-- Check Open Valences --
Status: pass
-- Check Geometry --
for those bonded
for those not bonded
Status: pass
-- Check Weird Bonds --
Status: pass
-- Check Number of Units --
Status: pass
acdoctor mode has completed checking the input file.
Running: /home/salome/pymol/envs/pygromosx/bin/bondtype -j full -i ANTECHAMBER_BOND_TYPE.AC0 -o ANTECHAMBER_BOND_TYPE.AC -f ac
Running: /home/salome/pymol/envs/pygromosx/bin/atomtype -i ANTECHAMBER_AC.AC0 -o ANTECHAMBER_AC.AC -p gaff
Info: Total number of electrons: 50; net charge: 0
Running: /home/salome/pymol/envs/pygromosx/bin/sqm -O -i sqm.in -o sqm.out
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
Running: /home/salome/pymol/envs/pygromosx/bin/am1bcc -i ANTECHAMBER_AM1BCC_PRE.AC -o ANTECHAMBER_AM1BCC.AC -f ac -p /home/salome/pymol/envs/pygromosx/dat/antechamber/BCCPARM.DAT -s 2 -j 1
Running: /home/salome/pymol/envs/pygromosx/bin/atomtype -f ac -p bcc -o ANTECHAMBER_AM1BCC.AC -i ANTECHAMBER_AM1BCC_PRE.AC
['/home/salome/pymol/envs/pygromosx/bin/parmchk2', '-i', '/home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/antechamber_tmp/aniline.mol2', '-f', 'mol2', '-o', 'aniline.frcmod']
['/home/salome/pymol/envs/pygromosx/bin/tleap', '-f', 'aniline.cmd']
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/prep to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/lib to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/parm to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/cmd to search path.
-f: Source aniline.cmd.
Welcome to LEaP!
(no leaprc in search path)
Sourcing: ./aniline.cmd
----- Source: /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.gaff
----- Source of /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.gaff done
Log file: ./leap.log
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/gaff.dat
Reading title:
AMBER General Force Field for organic molecules (Version 1.81, May 2017)
----- Source: /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.water.tip3p
----- Source of /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.water.tip3p done
Loading library: /home/salome/pymol/envs/pygromosx/dat/leap/lib/atomic_ions.lib
Loading library: /home/salome/pymol/envs/pygromosx/dat/leap/lib/solvents.lib
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.tip3p
Reading force field modification type file (frcmod)
Reading title:
This is the additional/replacement parameter set for TIP3P water
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ions1lm_126_tip3p
Reading force field modification type file (frcmod)
Reading title:
Li/Merz ion parameters of monovalent ions for TIP3P water model (12-6 normal usage set)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ionsjc_tip3p
Reading force field modification type file (frcmod)
Reading title:
Monovalent ion parameters for Ewald and TIP3P water from Joung & Cheatham JPCB (2008)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ions234lm_126_tip3p
Reading force field modification type file (frcmod)
Reading title:
Li/Merz ion parameters of divalent to tetravalent ions for TIP3P water model (12-6 normal usage set)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.chcl3
Reading force field modification type file (frcmod)
Reading title:
chloroform frcmod file
Using modified Bondi radii
Loading parameters: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/parmchk_tmp/aniline.frcmod
Reading force field modification type file (frcmod)
Reading title:
Remark line goes here
Loading Mol2 file: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/antechamber_tmp/aniline.mol2
Reading MOLECULE named ligand_1
Solute vdw bounding box: 8.593 7.203 3.895
Total bounding box for atom centers: 36.593 35.203 31.895
Solvent unit box: 56.496 56.496 56.496
Total vdw box size: 40.347 38.887 35.650 angstroms.
Volume: 55933.916 A^3
Total mass 28741.446 amu, Density 0.853 g/cc
Added 240 residues.
Checking Unit.
Building topology.
Building atom parameters.
Building bond parameters.
Building angle parameters.
Building proper torsion parameters.
Building improper torsion parameters.
total 7 improper torsions applied
Building H-Bond parameters.
Incorporating Non-Bonded adjustments.
Not Marking per-residue atom chain types.
Marking per-residue atom chain types.
(Residues lacking connect0/connect1 -
these don't have chain types marked:
res total affected
LI1 1
)
(no restraints)
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
Writing pdb file: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/tleap_tmp/anilineleap_CHCL3BOX.pdb
printing CRYST1 record to PDB file with box info
Quit
Exiting LEaP: Errors = 0; Warnings = 0; Notes = 0.
converted topology saved to /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/aniline_CHCL3BOX.top
40.3470000 38.8870000 35.6500000 90.0000000 90.0000000 90.0000000
converted coordinates saved to /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/aniline_CHCL3BOX.cnf
[8]:
ff.amber.solvate
[8]:
True
create top + cnf for aniline, solvated in TIP3P water¶
[9]:
ff.solventbox = "TIP3PBOX"
[10]:
system = gromos_system.Gromos_System(work_folder = "example_files/amber2gromos",
system_name = "aniline",
forcefield = ff,
auto_convert = True,
in_mol2_file = molecule,
in_gromosPP_bin_dir = gromosPP_bin_dir)
['/home/salome/pymol/envs/pygromosx/bin/antechamber', '-i', '/home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.mol2', '-fi', 'mol2', '-o', 'aniline.mol2', '-fo', 'mol2', '-s', '2', '-c', 'bcc', '-nc', '0']
Welcome to antechamber 21.0: molecular input file processor.
acdoctor mode is on: check and diagnose problems in the input file.
The atom type is set to gaff; the options available to the -at flag are
gaff, gaff2, amber, bcc, and sybyl.
-- Check Format for mol2 File --
Status: pass
Info: Ignoring Mol2 record type (@<TRIPOS>SUBSTRUCTURE).
Info: Finished reading file (/home/salome/PhD/pyg/PyGromosTools/examples/example_files/amber2gromos/aniline.mol2); atoms read (14), bonds read (14).
Info: Determining atomic numbers from atomic symbols which are case sensitive.
-- Check Unusual Elements --
Status: pass
-- Check Open Valences --
Status: pass
-- Check Geometry --
for those bonded
for those not bonded
Status: pass
-- Check Weird Bonds --
Status: pass
-- Check Number of Units --
Status: pass
acdoctor mode has completed checking the input file.
Running: /home/salome/pymol/envs/pygromosx/bin/bondtype -j full -i ANTECHAMBER_BOND_TYPE.AC0 -o ANTECHAMBER_BOND_TYPE.AC -f ac
Running: /home/salome/pymol/envs/pygromosx/bin/atomtype -i ANTECHAMBER_AC.AC0 -o ANTECHAMBER_AC.AC -p gaff
Info: Total number of electrons: 50; net charge: 0
Running: /home/salome/pymol/envs/pygromosx/bin/sqm -O -i sqm.in -o sqm.out
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
Running: /home/salome/pymol/envs/pygromosx/bin/am1bcc -i ANTECHAMBER_AM1BCC_PRE.AC -o ANTECHAMBER_AM1BCC.AC -f ac -p /home/salome/pymol/envs/pygromosx/dat/antechamber/BCCPARM.DAT -s 2 -j 1
Running: /home/salome/pymol/envs/pygromosx/bin/atomtype -f ac -p bcc -o ANTECHAMBER_AM1BCC.AC -i ANTECHAMBER_AM1BCC_PRE.AC
['/home/salome/pymol/envs/pygromosx/bin/parmchk2', '-i', '/home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/antechamber_tmp/aniline.mol2', '-f', 'mol2', '-o', 'aniline.frcmod']
['/home/salome/pymol/envs/pygromosx/bin/tleap', '-f', 'aniline.cmd']
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/prep to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/lib to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/parm to search path.
-I: Adding /home/salome/pymol/envs/pygromosx/dat/leap/cmd to search path.
-f: Source aniline.cmd.
Welcome to LEaP!
(no leaprc in search path)
Sourcing: ./aniline.cmd
----- Source: /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.gaff
----- Source of /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.gaff done
Log file: ./leap.log
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/gaff.dat
Reading title:
AMBER General Force Field for organic molecules (Version 1.81, May 2017)
----- Source: /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.water.tip3p
----- Source of /home/salome/pymol/envs/pygromosx/dat/leap/cmd/leaprc.water.tip3p done
Loading library: /home/salome/pymol/envs/pygromosx/dat/leap/lib/atomic_ions.lib
Loading library: /home/salome/pymol/envs/pygromosx/dat/leap/lib/solvents.lib
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.tip3p
Reading force field modification type file (frcmod)
Reading title:
This is the additional/replacement parameter set for TIP3P water
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ions1lm_126_tip3p
Reading force field modification type file (frcmod)
Reading title:
Li/Merz ion parameters of monovalent ions for TIP3P water model (12-6 normal usage set)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ionsjc_tip3p
Reading force field modification type file (frcmod)
Reading title:
Monovalent ion parameters for Ewald and TIP3P water from Joung & Cheatham JPCB (2008)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.ions234lm_126_tip3p
Reading force field modification type file (frcmod)
Reading title:
Li/Merz ion parameters of divalent to tetravalent ions for TIP3P water model (12-6 normal usage set)
Loading parameters: /home/salome/pymol/envs/pygromosx/dat/leap/parm/frcmod.chcl3
Reading force field modification type file (frcmod)
Reading title:
chloroform frcmod file
Using modified Bondi radii
Loading parameters: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/parmchk_tmp/aniline.frcmod
Reading force field modification type file (frcmod)
Reading title:
Remark line goes here
Loading Mol2 file: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/antechamber_tmp/aniline.mol2
Reading MOLECULE named ligand_1
Solute vdw bounding box: 8.593 7.203 3.895
Total bounding box for atom centers: 36.593 35.203 31.895
Solvent unit box: 18.774 18.774 18.774
Total vdw box size: 39.546 38.307 34.954 angstroms.
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
/bin/bash: /home/salome/pymol/envs/pygromosx/lib/libtinfo.so.6: no version information available (required by /bin/bash)
Volume: 52950.481 A^3
Total mass 21982.566 amu, Density 0.689 g/cc
Added 1215 residues.
Checking Unit.
Building topology.
Building atom parameters.
Building bond parameters.
Building angle parameters.
Building proper torsion parameters.
Building improper torsion parameters.
total 7 improper torsions applied
Building H-Bond parameters.
Incorporating Non-Bonded adjustments.
Not Marking per-residue atom chain types.
Marking per-residue atom chain types.
(Residues lacking connect0/connect1 -
these don't have chain types marked:
res total affected
LI1 1
WAT 1215
)
(no restraints)
Writing pdb file: /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/tleap_tmp/anilineleap_TIP3PBOX.pdb
printing CRYST1 record to PDB file with box info
Quit
Exiting LEaP: Errors = 0; Warnings = 0; Notes = 0.
converted topology saved to /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/aniline_TIP3PBOX.top
39.5462090 38.3065070 34.9536470 90.0000000 90.0000000 90.0000000
converted coordinates saved to /home/salome/PhD/pyg/PyGromosTools/examples/example_files/ambertools_pipeline/aniline_TIP3PBOX.cnf
[ ]:
[ ]:


Team Employee Profile
Manager Info
Obedia Lawrence
789
<EMAIL_ADDRESS>7
Engineer Info
Gerald Wright
789
<EMAIL_ADDRESS>GeraldW
Intern Info
Jessica Alba
898
<EMAIL_ADDRESS>Georgia Tech
This completes my team with the members needed.


The Category field searches on categories / classification codes. Some sources for our categories use plural terms, while others use singular terms. To return the greatest amount of relevant matches, the search process ignores spaces, punctuation, and any "s" at the end of words. Therefore the matching substances returned may not have the exact same spelling as a search term, but may have a similar category name instead.
Due to this merging and in order to generate quick AutoComplete results, the indicated value and substance totals for Category searches may not be accurate in the AutoComplete. Once a full search is run, the totals are correct.


Brief history about me
Foli Martin is my name, pursuing Bsc. Applied Technology at Brigham Young University, Idaho (BYU-Idaho), passed student of the University of Cape Coast and a multi-skilled individual situated in the Western part of Africa (Ghana).
As a web developer has been the best experience anyone could ever wish for. I have had enough experience and had done so many projects
Logo designing, banners, birthday or wedding flyers, business cards, invitation cards, these and many more. If you think of quality yet affordable designs then you are at the right place. Get in touch now and let's talk business.
As a web developer has been the best experience anyone could ever wish for. I have had enough experience and had done so many projects
Get in touch
Akosombo-Township
Eastern Region,Ghana
<EMAIL_ADDRESS><EMAIL_ADDRESS>+233-546-757-518
+233-505-154-037


Confirm that a data-main="index.js" with an inline config with a baseUrl works with a built script that has "index" as the top level define call. More info: 303.
Check console for messages


Amur Grapes
Desctription
Amur grapes have small flowers that bees find to be beeatuiful and a great source of nectar. The Amur grape is dioecious. The grapes themselves are convex elipsoid shaped, with a black or dark burgundy color.
The Amur grape vine has tendrils that like to get friendly and hug other
plants for support. The bark is dark, scaly and with vertical stripes on old shoots.
Young shoots are green, often with a reddish hue, reddish-brown in autumn.
Botany
Scientific Classification
- Eukaryote
- Plantae
- Vascular Plant
- Magnoliopsida
- Vitales
- Vitaceae
- Vitis
- V. amurensis
- Vitis
- Vitaceae
- Vitales
- Magnoliopsida
- Vascular Plant
- Plantae
The Amur grape is a tought little grape. It is grape at growing in areas that have frost because it is extremely frost resistant. Also it is resistant to anthracnose and ripe rot.
The Amur grape's name comes from the Amur Valley in China and Russia. The vines are sometimes used for natrual ground cover. This is because the leaves turn bright colors in fall


Coldplay axes tour plans for the environment
by Entertainment DeskLONDON: British band Coldplay will not tour to promote their new album, but are working on how to make their gigs environmentally sustainable, lead singer Chris Martin said.
The rock group, known for songs like Yellow, Paradise and Viva la Vida, will release their eighth studio album Everyday Life on Friday. The 52-minute record is made up of two halves, Sunrise and Sunset.
“We’re not touring this album. We’re taking time over the next year or two to work out how our tour (can not only) be sustainable but how can it be actively beneficial,” Martin told British broadcaster BBC in Jordan, where Coldplay will perform two shows on Friday to mark the album’s release.
“Our dream is to have a show with no single-use plastic, to have it be largely solar-powered.”
Coldplay will play a one-off show at London’s Natural History Museum on Monday to promote the album. All performance proceeds will go to environmental charity ClientEarth.
“This is expected to be the band’s only UK show of the ‘Everyday Life’ era,” a press release for the show said.
Coldplay last toured globally in 2016-2017 to promote album A Head Full of Dreams.
“All of us, in every industry, have to just work out what the best way of doing our job is … The hardest thing is the flying side of things,” Martin said.
Amid growing environmental concerns from consumers and young fans, several music artists have addressed climate change in lyrics or announced plans to improve their green credentials.
Rockers The 1975 teamed up with climate activist Greta Thunberg for a track on their upcoming album in which the teenage Swedish activist warns about climate change.
“It is fantastic to see world famous artists stepping up to protect the planet,” Gareth Redmond-King, head of Climate Change at the WWF conservation group, said in a statement.
“We all have a responsibility to lead by example in the face of this climate and nature crisis – inaction is not an option if we are to preserve our planet for future generations.”
REUTERS
Have something to add to the story? Share it in the comments below.


Olivier Beauchard (data preparation and processing)
Alexander Barth (code development and data interpolation)
Peter Herman (data preparation and interpretation)
Jean-Marie Beckers (code development)
Charles Troupin (data interpolation and visualisation)
Collect once,
Use many times
And create products with DIVA
Available from EMODnet Biology (see list on the web)
3 main living modes
Using co-variables to help for the interpolation
Main datasets: Zooplankton observations in the Baltic
3.
Findability
Accessibility
Interoperability
Reusability
Data EMODnet Biology
Tool DIVAnd v2.1.1: http://doi.org/10.5281/zenodo.1407912
Code and procedure Jupyter-notebooks:
Products available for download netCDF files:
https://dox.ulg.ac.be/index.php/s/EvIwSvTwhtJ6Tmu


DOCS
Simple, flexible deployment for your react app
React Deploy CLI manages deployment of code and assests of your react app to S3 bucket and maintains different versions.
Installation
To install react-deploy use the following command ...
Deployment
build and deploy your files to the S3 bucket by simple command .....
Listing
List the different versions of files you deployed the file by simple list command
Activation
Activate the files which you deployed by < 1 minutes
$ npm i react-deploy_
initializing react deploy file_
[?] What more would you like? (Press space to select)_
>_


Before retrieving your wallet address, it's recommended that you first write down your paper key and store it securely
so that your wallet can be recovered in the case your device was lost or stolen.
Incomplete wallet
All signing devices must be added to this multisig wallet before bitcoin addresses can be created.


Kiwako Sakamoto (Opening Speaker)
Kiwako is a data scientist who was part of the World Bank’s first data scientist team and later served as the first data scientist at the World Bank’s research department in Washington, DC. She was more recently the data science lead for the ambitious and controversial art project, DAU. She taught herself programming while working for a particle astrophysics project, IceCube, after dropping out of economics graduate school. She is happy about her choice and hasn’t looked back since.
Adam Borowski
Writing code at the speed of thought! Or voice! Or dance?
Adam graduated from an art school, but then turned to programming because it was more standardised. He writes front-ends for web applications for a living.
Agustin Ramos Anzorena
So, you have decided to become a Creative Technologist..!
Agustín Ramos Anzorena is an electronic artist, currently working on his Master thesis at the Master of Technology and Aesthetics of Electronic Arts, at UNTREF University, where he also dictates subjects on Creative Programming techniques and computationla thinking. In parallel, he teaches at other culturally important institutions, such as Centro Cultural San Martin, Centro Cultural de España en Buenos Aires, and the ORT Asociation.
His work explores light, shape and abstraction in visual composition. He is interested in the creation of small to medium spatial immersive experiences, as well as in the nature of computational procedures. His work has been exhibited in electronic art festivals in Buenos Aires, New York, France, Mexico and Brazil.
His residencies and artistic development programmes include: School for Poetic Computation (New York, USA), Center for Digital Arts and Experimental Media (University of Washington, Seattle, USA), The Recurse Center (New York, USA), Centre Intermondes “Espace International de Résidence Artistique” within Festival Zero1 (La Rochelle, France), the Understanding Visual Music International Conference for FullDome Projections, and he was also selected for the 2018/2019 INNOVART French/Argentinian Programme for artistic and scientific innovation research grant.
Anna Kapuścińska
Cause, trouble and fun of time
Software developer at Genomics England, previously at Clearcode. Working mostly with Python, always striving to learn more. Every day tries to make people lives a bit better. Loves astrophysics, traveling, books and coffee, sometimes in different order.
Carolyn Stransky
How AI is enhancing journalism
Carolyn is a frontend developer and former journalist based in Berlin. She’s a Mozilla Tech Speaker, co-organizer of BerlinJS and web chick at Blacklane.
Diego Valverde Garro
How I re-discovered my joy for programming through creative computing
Diego is a computer scientist from Costa Rica, currently based in Munich. He loves art, computers and is curious about many other topics. He strongly believes in the power learning by doing, and by sharing experiences with others.
Gargi Sharma
ptrace: The Sherlock Holmes of syscalls!
Gargi is a Software Engineer who recently attended the Recurse Center. Gargi loves everything about Systems Programming, shady syscalls and Modern Art.
Isabel Paehr
Isabel Paehr works as a media artist, game developer and researcher in Berlin. Paehr’s research interest in both her written and material work focuses on the relation between virtuality and concepts of the nonhuman. Her modes of presentation are exhibitions, city walks, online spaces, games and publications. She is 1/2 of the experimental game studio Topicbird. (http://isabelpaehr.com)
Jan-Erik Rediger
Jan-Erik is a Firefox Engineer at Mozilla and an active member of the Rust community since 2014. He coached at Rust workshops & runs conferences in Europe. To get away from computers he recently picked up scuba diving to see the world under water.
Knut Hühne
The Wikidata Query Interface: The world’s knowledge at your fingertips
Knut is a Berlin based software developer who loves all things open. As one of the organisers of the Berlin Open Knowledge Lab, he got to know the Wikidata project and continues to find more and more use-cases for it. He loves sharing his knowledge and thinks that Wikidata and Open Data in general can be a very empowering tool for everyone.
Lucas Werkmeister
LilyPond: programming beautiful musical scores
Lucas is a software developer at Wikimedia Deutschland, where he works on the software for Wikidata, a free knowledge database. In his spare time, he works on some projects (mostly Wikimedia-related), neglects too many others, plays the piano, and transcribes public-domain scores for LilyPond as a way to relax.
Max Hallinan
Max Hallinan wanted to be Philip Guston when he grew up. Now he’d rather grow up to be John McCarthy.
phoebe jenkins
phoebe has bounced around a number of different software engineering jobs, and is now currently working in security research. she is fascinated by all forms of esoteric computing, and would love to hear about whatever weird thing you’ve been working with lately.
Tamas Kadar
💩.la?!? the fascinating history and current state of IDNs!!
Tamas is a generalist working as a freelance consultant, automating all the things. He’s really into writing lately, and loves the world’s most pointless drink, a decaf latte.
Veit Heller
Veit is a jack of all trades, but a master of none. He frequently oscillates between compiler development, writing, creating generative art, and trying to get work done at his day job.


Class PlaneRef
A reference to a plane. The Plane is implemented as a struct, i.e. a value type. Sometimes it is necessary to have a parameter or member, which designates a plane but may be null (when the plane is not yet computed or not valid). This class works as an object replacement of the struct Plane.
Inheritance
System.Object
PlaneRef
Inherited Members
System.Object.Equals(System.Object)
System.Object.Equals(System.Object, System.Object)
System.Object.GetHashCode()
System.Object.GetType()
System.Object.MemberwiseClone()
System.Object.ReferenceEquals(System.Object, System.Object)
System.Object.ToString()
Namespace: CADability
Assembly: CADability.dll
Syntax
public class PlaneRef
Constructors
| Improve this Doc View SourcePlaneRef(Plane)
Standard and only constructor, wrapping the given Plane.
Declaration
public PlaneRef(Plane p)
Parameters
| Type | Name | Description |
|---|---|---|
| Plane | p | The Plane to wrap |
Methods
| Improve this Doc View SourceFindCommonPlane(GeoPoint[], out Plane)
Yields a common plane of the cloud of points, if there is one. If there is no common plane the result may be not optimal (residual is not minimal)
Declaration
public static bool FindCommonPlane(GeoPoint[] Cloud, out Plane commonPlane)
Parameters
| Type | Name | Description |
|---|---|---|
| GeoPoint[] | Cloud | the cloud of points |
| Plane | commonPlane |
Returns
| Type | Description |
|---|---|
| System.Boolean | the plane, may be null |
Operators
| Improve this Doc View SourceImplicit(Plane to PlaneRef)
Operator to seamlessly use a Plane as a PlaneRef
Declaration
public static implicit operator PlaneRef(Plane p)
Parameters
| Type | Name | Description |
|---|---|---|
| Plane | p |
Returns
| Type | Description |
|---|---|
| PlaneRef | The resulting PlaneRef |
Implicit(PlaneRef to Plane)
Operator to seamlessly use a PlaneRef as a Plane
Declaration
public static implicit operator Plane(PlaneRef pr)
Parameters
| Type | Name | Description |
|---|---|---|
| PlaneRef | pr | The PlaneRef to convert |
Returns
| Type | Description |
|---|---|
| Plane | The resulting Plane |


{% extends "base.html" %} {% block title %}Password Changed{% endblock %} {% block body %}
Your password has been changed. You can now Sign In.


Login
Contact Us
704-960-3205
Lets Connect
We'd love to help you start exceeding your CX goals.
First Name*
Last Name*
Buisness Email
(privacy policy)*
Company*
Tell us more about yourself;*
Would you like to subscribe to our Customer Experience blog?*
Yes
No


Note
This tutorial was generated from an Jupyter notebook that can be downloaded here.
Light travel time delay¶
A simple tutorial on how the finite speed of light affects exoplanet light curves and how to account for this in starry
.
Imports¶
[1]:
from starry.kepler import Primary, Secondary, System
import numpy as np
import matplotlib.pyplot as pl
Instantiating a simple system¶
Let’s instantiate a simple limb-darkened star and a hot Jupiter on a 10-day period with a dipole map:
[4]:
star = Primary()
star[1] = 0.40
star[2] = 0.26
planet = Secondary()
planet.L = 1e-3
planet.r = 0.1
planet.porb = 10
planet.prot = 10
planet.a = 22
planet[1, 0] = 0.5
By default, starry
does not compute the effects of light travel time. The main reason for this is that all the stuff in starry
is unitless: the primary’s physical properties (radius and luminosity) are fixed at unity, and the secondary’s parameters are all specified relative to these quantities. In order to compute the light travel time within the system, starry
needs to know the actual size of the orbits. Since all distances are measured relative to the primary’s radius, to turn
light travel effects on all you need to do is tell starry
how big the primary is. This is done by setting the r_m
(radius in meters) parameter of the Primary
instance:
[6]:
system = System(star, planet)
star.r_m = 0
I set it to zero for now, which tells starry
the star’s radius is zero. Quite unphysical, but the r_m
parameter is only used to compute the light travel time, so this effectively tells starry
that light travels across the system instantaneously. Let’s plot the system light curve over one orbital period:
[8]:
time = np.concatenate((np.linspace(0, 0.5, 10000, endpoint=False),
np.linspace(0.5, 4.5, 100, endpoint=False),
np.linspace(4.5, 5.5, 10000, endpoint=False),
np.linspace(5.5, 9.5, 100, endpoint=False),
np.linspace(9.5, 10, 10000)))
phase = time / 10.
system.compute(time)
fig, ax = pl.subplots(1, figsize=(16, 4))
ax.plot(phase, system.lightcurve);
ax.set_xlabel('Orbital phase', fontsize=16);
ax.set_ylabel('Flux', fontsize=16);
transit = phase[np.argmax(planet.Z)]
eclipse = phase[np.argmin(planet.Z)]
ax.axvline(transit, ls='--', lw=1);
ax.axvline(eclipse, ls='--', lw=1);
print("Transit: %.6f" % transit)
print("Eclipse: %.6f" % eclipse)
Transit: 0.000000
Eclipse: 0.500000
A couple remarks:
I added higher time resolution near transit and secondary eclipse so we can time things accurately
I computed and marked the phase corresponding to the largest value of
z
(when the planet is closest to the observer): this is the time of transit, accurate to within our time grid spacingI also computed and marked the phase corresponding to the smallest value of
z
(when the planet is farthest from the observer): this is the time of secondary eclipse
As expected, transit occurs at a phase of exactly 0 and eclipse at a phase of exactly 1/2.
Accounting for the light travel time¶
Now, let’s tell starry
to compute the effects of light travel time by giving our star an actual physical radius. The r_m
parameter is the radius of the star in meters, so if our star is a Sun-like star, we simply tell starry
[9]:
star.r_m = 6.95700e8
Let’s recompute and plot the light curve:
[11]:
eps = 1e-3
time = np.concatenate((np.linspace(0, 0.5, 100000, endpoint=False),
np.linspace(0.5, 5 - eps, 100, endpoint=False),
np.linspace(5 - eps, 5 + eps, 1000000, endpoint=False),
np.linspace(5 + eps, 9.5, 100, endpoint=False),
np.linspace(9.5, 10, 100000)))
phase = time / planet.porb
system.compute(time)
fig, ax = pl.subplots(1, figsize=(16, 4))
ax.plot(phase, system.lightcurve);
ax.set_xlabel('Orbital phase', fontsize=16);
ax.set_ylabel('Flux', fontsize=16);
transit = phase[np.argmin(np.abs(planet.X) + (planet.Z < 0))]
eclipse = phase[np.argmin(np.abs(planet.X) + (planet.Z > 0))]
ax.axvline(transit, ls='--', lw=1);
ax.axvline(eclipse, ls='--', lw=1);
print("Transit: %.6f" % transit)
print("Eclipse: %.6f" % eclipse)
Transit: 0.999941
Eclipse: 0.500059
The effect is super tiny in this case, but there is now a small offset in both the time of transit and of secondary eclipse! In starry
, the time delay is computed relative to the barycenter, so transits happen early (since the planet is closer to the observer than the barycenter) and eclipses happen late (since the planet is farther). We can verify that the phase difference between secondary eclipse and a phase of 0.5 is just a / c
, the time light takes to travel from the planet to
the barycenter:
[12]:
print("Time delay from starry (s): %.8f" % ((eclipse - 0.5) * planet.porb * 86400))
Time delay from starry (s): 51.05324160
[13]:
c = 299792458. # m / s
RSUN = 6.957e8 # m
a = planet.a * star.r_m
print("Time delay from common sense (s): %.8f" % (a / c))
Time delay from common sense (s): 51.05331903
Not bad! Note that they are in fact slightly different, for a rather subtle reason. There’s actually no closed-form way to compute the light travel time delay at arbitrary points in the light curve! Let me clarify: it’s (very) easy to compute what the delay dt
is given knowledge of where the planet is in the orbit at time t
. But that calculation tells me what the light curve will look like at time t + dt
, when the information actually reaches the observer (well, technically, when
it reaches the reference point). Our observations are at time t
, not t + dt
, so what we actually need to know is where the planet was in its orbit at time t - dt
. This may sound easy, but if you think about it, we are essentially asking to know the position
\(x'(t) = x\bigg(t - dt\Big(x'(t)\Big)\bigg)\)
which is a transcendental equation! The difficulty boils down to the fact that \(dt\) is a function of the planet’s retarded position, so it’s a function of the very variable whose value we seek.
To get around this, what we do in starry
is we Taylor expand the equation above to second order, so we get a pretty good approximation to \(dt(x'(t))\). We then re-compute the orbital position at the retarded time and use that to compute light curves. So, long story short, the time delay computed by starry
is not exact. In principle, we could take the expansion out to higher order. If you have an application that needs this extra accuracy, please let us know!
Just for fun¶
Finally, just for fun, here’s a bunch of light curves with ridiculous (and very unphysical) light travel time delays, obtained by setting the stellar radius to very large (and very unphysical) values. I’m only plotting the planet flux so we can better see the behaviour of the phase curve.
[14]:
time = np.linspace(0, 10, 100000)
phase = time / planet.porb
fig, ax = pl.subplots(1, figsize=(16, 4))
for scale in [1, 10, 100, 1000, 1500]:
star.r_m = 6.95700e8 * scale
system.compute(time)
ax.plot(phase, planet.lightcurve, label="scale = %d" % scale);
ax.set_xlim(0.4, 0.7)
ax.set_xlabel('Orbital phase', fontsize=16);
ax.set_ylabel('Flux', fontsize=16);
ax.legend();
The cool thing you can see from these is that the light travel time also affects the phase curves, although keep in mind the effect is very small! Remember that these are unphysical systems: the purple curve corresponds to a planet traveling at \(0.5c\) (!!) You’d probably have all sorts of relativistic effects in that case that starry
does not model.


Valve Site Map
Location Of Valve Groups
Description of Valve Groups
Valve Group #1
Land mark to #1 valve: Well
- Valve #1 Satellite_1:20 Flowers along side walk
- Valve #2 Satellite_1:19 Well Water Drip Line
- Valve #3 Satellite_1:14 Barbecue Clover Area
- Valve #4 Satellite_1:18 Well Clover Area
- Valve #5 Satellite_1:15 Triangle Pool Area
- Valve #6 Satellite_1:17 Dragon Fruit — Fruit Tree Drip Line
- Valve #7 Satellite_1:16 Pool Fence Area
Valve Group #2
Land mark to #1 valve: Steps
- Valve #1 Satellite_1:13 Lemon Tree Drip Line near Steps
- Valve #2 Satellite_1:25 Middle Clover Near Well
- Valve #3 Satellite_1:12 Middle Clover Near Barbecue
- Valve #4 Satellite_1:11 Drip Line along garage
Valve Group #3
Land mark to #1 valve: Door
- Valve #1 Satellite_1:24 Flowers Toward Garage
- Valve #2 Satellite_1:21 Grass Zone Away From Door
- Valve #3 Satellite_1:22 Grass Toward Door
- Valve #4 Satellite_1:23 Flowers on Opposite Side of Garage
Valve Group #4
Land mark to #1 valve: Side Walk
- Valve #1 Satellite_2:2 Upper area Near Property Line
- Valve #2 Satellite_2:4 On Property Side of Valve #3
- Valve #3 Satellite_2:3 Next to Valve 4
- Valve #4 Satellite_2:1 Spray Area Next to Remote
- Valve #5 Satellite_2:5 Sprayers along Drive Way
- Valve #6 Satellite_2:6 Lower area near Property Line
Valve Group #5
Land mark to #1 valve: Nearest Solar Panels
- Valve #1 Satellite_1:9 Waters Fruit Trees on Block #9
- Valve #2 Satellite_1:1 Hill Sprayers next to Large Rock
- Valve #3/#4 Valves are tied together Satellite_1:2. Spray area rest of bank.
- Valve #5 Satellite_1:6 Waters Avocado Block #6
Valve Group #6
Land mark to #1 valve: Property Line
- Valve #1 Satellite_2:13 Waters Avocado Block #4
- Valve #2 Satellite_2:14 Waters Avocado Block #10
- Valve #3 No Connection
- Valve #4 Satellite_2:17 Drip Line and Sprayers along Road
- Valve #5 No Connection
- Valve #6 No Connection
- Valve #7 No Connection
Valve Group #7
Land mark to #1 valve: Cindy’s House
- Valve 1 Satellite_3:4 Not Connected
- Valve 2 Satellite_3:3 Not Connected
- Valve 3 Satellite_3:1 Avocado Block 5
- Valve 4 Satellite_3:6 Not Connected
- Valve 5 Satellite_3:5 Avocado Block 11
- Valve 6 Satellite_3:2 Drip Line Down the Hill
Valve Group #8
Land mark to #1 valve: Cindy’s House
- Valve #1 Satellite_3:13 Avocado Block #1
- Valve #2 Satellite_3:14 Avocado Block #2
- Valve #3 Satellite_3:18 Not Connected
- Valve #4 Satellite_3:17 Not Connected
- Valve #5 Not Connected
- Valve #6 Satellite_3:15 Avocado Block #3
- Valve #7 Satellite_3:19 Top Most Sprayers
Valve Group #9
Land mark to #1 valve: Road
- Valve #1 Satellite_3:11 this side of driveway
- Valve #2 Satellite_3:12 opposite side of driveway
Valve Group #10
Land mark to #1 valve: Road
- Valve #1 Not Connected
- Valve #2 Satellite_1:3 Drip line along side of Road
- Valve #3 Satellite_1:7 Avocado Bank 7
- Valve #4 Satellite_1:8 Avocado Bank 8


Open Angel Arena ChangeLogs
OAA Patch Notes 3.13.4
OAA Patch Notes 3.13.5
OAA Patch Notes 3.13.6
OAA Patch Notes 3.13.7
OAA Patch Notes 3.13.8
OAA Patch Notes 3.13.9
OAA Patch Notes 3.13.10
OAA Patch Notes 4.0.0
OAA Patch Notes 4.1.0
OAA Patch Notes 4.2.1
OAA Patch Notes 4.2.2


Copyright ©2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This is a W3C Note produced by the XML Core Working Group to supplement the XML Infoset specification. It is not a normative part of that specification.
This document is a work in progress representing the current consensus of the XML Core Working Group. Publication as a Note does not imply endorsement by the W3C membership.
Comments on and corrections to this Note and the RDF schema itself may be sent to the public mailing list<EMAIL_ADDRESS>An archive is available at http://lists.w3.org/Archives/Public/www-xml-infoset-comments/.
A list of current W3C technical documents can be found at the Technical Reports page.
The XML Infoset specification [1] defines a number of Information Items and their properties. The referenced RDF schema [2] is a formal description of the Infoset. We hope that it will be useful as an aid to understanding the Infoset and, perhaps, for validating infosets serialized as RDF instances.
It should be emphasized that this RDF schema is not normative. It is not the only RDF schema that could be constructed for the Infoset, and non-RDF serializations of the Infoset may also be useful.
There is a comment near the top of the schema specifying the version of the XML Infoset specification that it corresponds to. If errors are found in the schema it will be corrected without changing its namespace name. If the schema is changed to correspond to a new version of the Infoset, the namespace name will be changed.


Report a bug
If you spot a problem with this page, click here to create a Bugzilla issue.
Improve this page
Quickly fork, edit online, and submit a pull request for this page.
Requires a signed-in GitHub account. This works well for small changes.
If you'd like to make larger changes you may want to consider using
a local clone.
Change Log: 2.054
Download D 2.054
released Jul 10, 2011
New/Changed Features
- Implement @safe
- Implement @property
- Automatic inference for @safe, pure, nothrow
- Allow labelled break and continue in CTFE
- Warn about switch case fallthrough
- Pointers are now supported in CTFE
- Heap-allocated structs are now supported in CTFE
- Added SSSE3 instructions to inline assembler
- Change from warning to deprecated: non-final switch statements must have a default statement
- Change from warning to deprecated: function is hidden by function
- Add warning about switch case fallthrough
- Add warning about calling pure nothrow functions and ignoring the result
- Allow associative arrays with key of type bool
- Added inference for purity and safety
- Change win32 dmd to not emit a map file unless asked for with -map
- Added -property switch
- Bugzilla 5823: @property call syntax restriction not implemented
- Added core.sys.posix.netdb
- For functions which have a version which takes a core.time.Duration and another version which takes an integral value, the version which takes an integral value is now scheduled for deprecation.
- std.array.insertInPlace supports inserting of multiple ranges/elements in one go
- Added std.array.uninitializedArray and std.array.minimallyInitializedArray
- Various functions in std.string were renamed to match Phobos' naming conventions and be properly camelcased. The old names are still there but have been scheduled for deprecation.
- Various functions in std.uni were renamed so that they don't have "Uni" in their name, since it was decided that it was not desirable to repeat a module's name in its functions' names. The old names are still there but have been scheduled for deprecation.
- std.ctype has been scheduled for deprecation. std.ascii has been added to replace it.
- Major performance improvements for std.algorithm.sort
- std.string.atoi has been removed; replace it with std.conv.to!int
- Switched to using posix.mak instead of various .mak files
Druntime Bugs Fixed
- Bugzilla 4323: std.demangle incorrectly handles template floating point numbers
- Bugzilla 5272: Postblit not called on copying due to array append
- Bugzilla 5956: Undocumented mangling of struct value
- Bugzilla 6135: Thread/GC interaction bug on OS X
Library Bugs Fixed
- Bugzilla 2108: regexp.d: The greedy dotstar isn't so greedy
- Bugzilla 3136: Incorrect and strange behavior of std.regexp.RegExp if using a pattern with optional prefix and suffix longer than 1 char
- Bugzilla 3457: rdmd fails silently in a particular setup where the compiler is not the expected
- Bugzilla 3479: writef/writefln: positional precision not working
- Bugzilla 3564: Rdmd failing to link external C libraries
- Bugzilla 3752: File.byLine fetches lines in a confusing manner
- Bugzilla 4367: std.regex: Captures is not a random access range
- Bugzilla 4574: std.regex: breaks with empy string regex
- Bugzilla 4608: std.string.chomp documentation mismatch implementation
- Bugzilla 5019: In std.regex, empty capture at end of string causes error
- Bugzilla 5059: String assignment in foreach loop breaks immutability
- Bugzilla 5458: scope for function parameters is not documented
- Bugzilla 5511: std.regex optional capture with no-match cause error
- Bugzilla 5598: rdmd does not fail on invalid filename
- Bugzilla 5673: Add lookahead and forgetful matching support std.regex
- Bugzilla 5705: Swapping identical struct with hasElaborateAssign causes "overlapping array copy" exception
- Bugzilla 5836: std.typetuple.staticIndexOf's example code missing %s in call to writefln
- Bugzilla 5857: std.regex (...){n,m} is bogus when (...) contains repetitions
- Bugzilla 5869: std.thread needs to be removed
- Bugzilla 6026: DLL example needs update due to missing core.dll_helper
- Bugzilla 6076: regression, std.regex: "c.*|d" matches "mm"
- Bugzilla 6101: Documentation for dead modules still distributed with DMD
- Bugzilla 6113: singletons in std.datetime are not created early enough
- Bugzilla 6193: Appender.clear() functionality or documentation
DMD Bugs Fixed
- Bugzilla 693: 'this' can't be used as an alias parameter for a mixin
- Bugzilla 1373: typeof(func).stringof fails when func has parameters.
- Bugzilla 1411: ref Tuple should transform to Tuple of refs
- Bugzilla 1570: Wrong return for address operator
- Bugzilla 2180: filename error with #line
- Bugzilla 2521: Not possible to return immutable value by ref
- Temp destructors now called if exception is thrown
- Bugzilla 2625: Creating new struct with literal bypasses immutability of members if struct is in array
- Bugzilla 3147: Incorrect value range propagation for addition
- Bugzilla 3359: Cannot parse pure/const/immutable functions with inferred return type
- Bugzilla 3445: partial fix
- Bugzilla 3511: ref return property confused with property setter
- Bugzilla 3632: modify float is float to do a bitwise compare
- Bugzilla 3688: Can't have declaration with assignment to const/immutable inside if condition
- Bugzilla 3722: A method without an in contract should always succeed, even if overridden
- Bugzilla 3799: isStaticFunction trait evaluates to true for non-static nested functions
- Bugzilla 4031: Should be able to access const value-type globals from pure functions
- Bugzilla 4040: const/immutable on the right in auto return class methods
- Bugzilla 4063: [CTFE] key not found in AA gives bad error message
- Bugzilla 4065: [CTFE] AA "in" operator doesn't work
- Bugzilla 4107: Duplicate documentation for member function templates
- Bugzilla 4132: pointer arithmetic accepted in @safe functions
- Bugzilla 4170: Missing line number on compile-time array index
- Bugzilla 4258: "auto ref" doesn't work in one or more cases
- Bugzilla 4448: [CTFE] labeled break doesn't work in CTFE
- Bugzilla 4494: ICE(cod1.c) Array literal filled with results of void function
- Bugzilla 4633: typeof({return 1;}()) declaration fails if inside main
- Bugzilla 4661: Array Literal Incompatible Type Error Msg Should Include Line Number
- Bugzilla 4706: Overloading auto return w/ non-auto return = strange error msg
- Bugzilla 4745: Non-uniform handling of commas in static initialization of structs
- Bugzilla 4885: Uninitialize Pointers Allowed in @safe code
- Bugzilla 4910: [CTFE] Cannot evaluate a function that has failed at once
- Bugzilla 4963: ICE(type.c:320) for struct append where T.sizeof < 3
- Bugzilla 4969: nothrow check can't handle multiple catches
- Bugzilla 5088: Cannot cast const(int) to long in @safe function
- Bugzilla 5258: [CTFE] Stack overflow with struct by ref
- Bugzilla 5284: Array ops punch through const system
- Bugzilla 5327: Creating new struct with literal bypasses immutability of members of members of the struct
- Bugzilla 5396: [CTFE] Invalid code with nested functions in CTFE
- Bugzilla 5415: @Safe functions not working
- Bugzilla 5497: -- now produces error message instead of wrong code
- Bugzilla 5551: opUnary-opBinary conflict
- Bugzilla 5574: Struct destructor freaks out when an array of struct with single element is instantiated inside a class
- Bugzilla 5615: [CTFE] std.string.indexOf broken at compile time
- Bugzilla 5633: [CTFE] ICE(constfold.c): is expression with struct, struct pointer, array literal...
- Bugzilla 5657: Temporary object destruction
- Bugzilla 5659: Conditional operator, array literal, and std.traits.CommonType return a wrong common type
- Bugzilla 5676: [CTFE] segfault using tuple containing struct that has opAssign
- Bugzilla 5682: [CTFE] Silently wrong result possibly related to operator overloading and expression order
- Bugzilla 5693: Segfault with address of template struct opCall
- Bugzilla 5708: [CTFE] Incorrect string constant folding with -inline
- Bugzilla 5771: Template constructor and auto ref do not work
- Bugzilla 5819: DMD doesn't error/warn about illegal asm for 64bit mode
- Bugzilla 5845: Regression(2.041) [CTFE] "stack overflow" with recursive ref argument
- Bugzilla 5856: overloading on const doesn't work for operator overload
- Bugzilla 5859: Declaration inside if condition doesn't call destructor
- Bugzilla 5861: Wrong filename in error message when an invalid delegate in a template parameter is typeof()-ed
- Bugzilla 5885: wrong codegen for OPu32_d
- Bugzilla 5897: unrelated struct type casting should ignite construction
- Bugzilla 5936: Invalid code with nested functions in CTFE
- Bugzilla 5946: failing lookup 'this' from function in template
- Bugzilla 5954: [CTFE] enum structs with ctor
- Bugzilla 5959: Return by reference with nested function should be allowed
- Bugzilla 5962: Template function declaration with prefixed storage class and auto occurs conflict
- Bugzilla 5963: iasm does not accept 64bit integer literal
- Bugzilla 6001: [CTFE] ICE(interpret.c) mutating ref array
- Bugzilla 6015: [CTFE] Strange behavior of assignment appears in a situation
- Bugzilla 6049: [CTFE] Array literals of structs with invariant() are wrong
- Bugzilla 6052: [CTFE] Struct elements in an array are treated like reference type
- Bugzilla 6053: [CTFE] Two ICEs involving pointers (dereference and assign; pointer variable on stack)
- Bugzilla 6054: [CTFE] ICE when returning a returned compile-time associative array containing a key of an idup-ed array literal
- Bugzilla 6059: Incompatible types in array literal shows __error and error
- Bugzilla 6072: [CTFE] Regression(git master): Cannot declare variable inside an 'if' condition
- Bugzilla 6075: Cannot set value to associative array from a weakly-pure function when the value type has a (pure) opAssign
- Bugzilla 6077: [CTFE] Cannot append null array to null array.
- Bugzilla 6078: [CTFE] ICE on foreach over array struct member which is null
- Bugzilla 6079: [CTFE] Array index out of bound detection is off-by-one
- Bugzilla 6090: DDoc parenthesis escape issues.
- Bugzilla 6100: [CTFE] Regression: struct return values wrong if used in array initializer
- Bugzilla 6109: 'nothrow' does not check slice indices
- Bugzilla 6111: Escaping reference to local variable not detected
- Bugzilla 6119: Assertion failure: '0' on line 1118 in file 'glue.c'
- Bugzilla 6120: [CTFE] ICE on calling constructor of template struct with -inline in function/delegate literal.
- Bugzilla 6123: [CTFE] Cannot call a template member method inside delegate/function literal with -inline.
- Bugzilla 6137: [CTFE] Foreach on semantically wrong initialized array crashes the compiler
- Bugzilla 6145: Meaningless second error message for complex size of static array
- Bugzilla 6150: runnable/testsocket.d
- Bugzilla 6158: winsamp and dhry samples need an update
- Bugzilla 6161: iasm opcode family Jcc use absolute address instead of relative for functions
- Bugzilla 6164: [CTFE] Local arrays in a recursive local function behave funny
- Bugzilla 6198: [GSoC] ICE(e2ir.c) With circular import
- Bugzilla 6229: %= and /= no longer work on char type
- Bugzilla 6230: Member functions can no longer be weakly pure
- Bugzilla 6234: 64-bit array append generates inline code to copy new data, but does not call postblit
- Bugzilla 6241: test sdtor.d on osx not catching
- Bugzilla 6242: Disallow inoperant "in" contracts
- Bugzilla 6264: ICE on testing opSlice in static if
- Bugzilla 6267: Can't increment alias this'd struct from ref return
- Bugzilla 6279: Regression(2.054 beta): array-vararg with pointer type not working in safe code
Copyright © 1999-2023 by the D Language Foundation | Page generated by
Ddoc on Wed Mar 1 14:57:13 2023


Quick! The ring never reached Mount Doom and if Middle Earth is to be saved, then Gandalf must shoulder the burden alone. Will you save Middle Earth or tear all else down to claim the ring for yourself?


MicroCanvas Examples
Code examples
Minimal code example
Sprite loading & animation example
Cross-platform support example
Chiptune example
(note: currently broken, lib needs refactoring)
Games
Code Invaders
Snake


3.5. Shear Building: Synthetic Ground Motion¶
Consider the problem of uncertainty quantification in a three story shear building where the ground shaking will be represented by sythetic ground motion records based on two methods ([VPD18], [DD18])
The exercise will use the OpenSees, OpenSees, structural generators. For the OpenSees generator the following model script, ShearBuilding3.tcl , is used:
Warning
Do not place the file in your root, downloads, or desktop folder as when the application runs it will copy the contents on the directories and subdirectories containing this file multiple times (a copy will be made for each sample specified). If you are like us, your root, Downloads or Documents folders contains and awful lot of files and when the backend workflow runs you will slowly find you will run out of disk space!
3.5.1. Vlacho-Papakonstantinou-Deodatis Method¶
We will first demonstrate the steps to perform a sampling analysis to study the effects of earthquake magnitude, site-source distance, and soil velocity on structural dynamic responses, using the Vlacho-Papakonstantinou-Deodatis syntheic ground motion model.
To perform a Sampling or Forward propagation uncertainty analysis the user would perform the following steps:
Upon opening the application the UQ tab will be highlighted. In is panel, keep the UQ engine as that selected, i.e. Dakota, and the UQ Method Category as Forward Propagation, and the Method field as LHS (Latin Hypercube). Change the #samples field to
100
as shown in the following figure.
The GI panel will not be used for this run; For the time being leave the default values as is, and they will be automatically updated based on the information entered in the remaining tabs.
Next select the SIM panel from the input panel. This will default in the MDOF model generator. From the Model Generator pull down menu select OpenSees and select the example
3-story frame model
. For recording story responses, we also specify the node numbers on a column line (e.g., 1, 2, 3, 4 in the OpenSees model).
Next select the EVT panel. From the Load Generator pull down menu select the Stochastic Ground Motion option. This will present a new page of stochastic loading models. We first use the “Vlachos et al. (2018)” and for the three earthquake parameters: magnitude, distance, and shear-wave velocity, we define variables which will be randomized later in the RV panel
Next choose the FEM panel. Here we will change the entries to use Rayleigh damping, with Rayleigh factor chosen using the first and second modes.
We will skip the EDP panel leaving it in it’s default condition, that being to use the Standard Earthquake EDP generator.
For the RV panel, we will enter the distributions and values for our random variables. For demostration purposes, we assume all three variables follow normal distributions: the magnitude has a mean of 7 and standard deviation of 1; the distance has a mean of 20 km and standard deviation of 5 km; and the soil velocity has a mea of 259 m/s and standard deviation of 50 m/s.
Next click on the Run button. This will cause the backend application to launch Dakota. When the analysis is complete the RES tab will be selected and the results will be displayed. The results show the values for the mean and standard deviation.
If the user selects the Data tab in the RES panel, they will be presented with both a graphical plot and a tabular listing of the data. By left- and right-clicking with the mouse in the individual columns the axis changes (left mouse click controls vertical axis, right mouse click the horizontal axis). For example, we can now see the influences from the magitude (\(M\)), distance (\(R\)), and soil velocity (\(V\)) on the 1st stroy peak story drift ratio (\(1-PID-1-1\)).
3.5.2. Dabaghi-Der Kiureghian Method¶
The Dabaghi-Kiureghian model looks into the near-fault ground motion pulse feature and can generate pairs of synthetic pulse-like and non-pulse-like components in appropriate proportions. In this example, we would like to (1) understand the effects from the randomness in site-source distance (as similar but comparable to the first example above) and (2) compare the differences in structural responses due to the distinct characteristics of pulse-like and non-pulse-like records.
All the configurations are maintained the same as the first example except in the EVT panel, we select the “Dabaghi & Der Kiureghian (2018)” method. And we first fix the fault type to “Stike-Slip” and enable both the pulse-like and non-pulse-like records.
For the Depth to Top of Rupture Plane, we specify 0.0 km as a constant; and for the other earthquake parameters ( moment magnitude, closest distance to the site, parallel distance, and angel), we define their values as the figure shown in below. The random varaiable average shear-wave velocity (V) will be specified in the RV panel.
In the RV panel, we specify the normal distribution for the R variable.
In the RES panel, similar to the first example, the maximum story drift ratio and peak acceleration demands are recorded (e.g., 1st story 1-PID-1-1 and 3rd floor 1-PFA-3-1). And we could examine the influence from the site soil velocity on the 1st story peak story drift ratio.
The second part of this example is to compare the pulse-like and non-pulse-like records. So, we navigate back to the EVT panel and first select the “Only pulse-like” and then the “Non-pulse-like only” to run the analysis again. As seen in the figure below, the non-pulse-like group, on average, results in 10% to 15% higher structural responses in this example.
- VPD18
Vlachos, C., Papakonstantinou, K. G., & Deodatis, G. (2018). Predictive model for site specific simulation of ground motions based on earthquake scenarios. Earthquake Engineering & Structural Dynamics, 47(1), 195-218.
- DD18
Dabaghi, M., & Der Kiureghian, A. (2018). Simulation of orthogonal horizontal components of near‐fault ground motion for specified earthquake source and site characteristics. Earthquake Engineering & Structural Dynamics, 47(6), 1369-1393.


About
Generating a code coverage report for iOS and OSX projects requires a mish-mash of tools and steps. Here we've glued them all together into something that (hopefully) just works. All it took was a little Java, some Perl, a few shell scripts, a couple of Ruby Gems . . . and now you can:
- Generate a report with minimal steps.
- Output to the terminal as well as produce a detailed report in build-server friendly HTML format.
- Use the optional coverage checker, for example in CI builds to check minimum test coverage - failing the build if coverage falls below the required amount.
- Use it for free for both commercial and open-source projects!
Swift? Sorry, no dice
As yet there's no way to generate code coverage reports for Swift. If, like us, you'd like to see this implemented by Apple, please vote on this issue.


Oh, snap
It seems the client application is misconfigured. You may put yourself at risk in this path.
{{ if .ProceedTo }}If you're sure about the current situation, you can proceed to the client application. If you feel unsure, you can start from the home page in this website.
{{ else }}You may start from the home page in the current website or you can get back to the original (external) website.
{{ end }}Error code: {{ .ErrorCode }}


We redefine content!
- strategize turn-key initiatives
- exploit enterprise initiatives
- aggregate one-to-one users
- incentivize compelling e-markets
- enable e-business synergies
- synergize granular vortals
- optimize bricks-and-clicks paradigms
- evolve vertical relationships
- envisioneer e-business e-markets
- empower front-end web services
- grow frictionless methodologies
- brand front-end action-items
- utilize innovative solutions
- syndicate visionary paradigms
- drive cross-media systems


The One & Only
wedding event
You’re invited to a very special
occasion: Enjoy 20% off our
collection of gorgeous gowns and
bridesmaid dresses, plus big-day
finishing touches like veils, hair
pins and more.*
Online & in select stores.
Use code LOVE.
For a limited time only.
SHOP FOR THE BRIDE >
SHOP FOR THE BRIDESMAID >
Know someone who’s engaged?
FORWARD TO A BRIDE-TO-BE >
*Discount valid on purchases of full-priced bridal gowns, bridesmaid dresses, and women’s wedding accessories at jcrew.com and in J.Crew Wedding store locations from February 19, 2013 12:01am ET through March 3, 2013 11:59pm ET only. Offer is not valid on phone orders. Offer cannot be applied to previous purchases or the purchase of gift cards and cannot be redeemed for cash or used in combination with any other offer. Discount does not apply to the following: the Percy Gown, the Carenna Gown, the Sara Lace Gown, the Carina Gown, and the Clover Gown. Terms of offer are subject to change.
Please add<EMAIL_ADDRESS>to your address book to ensure our emails reach your inbox. If you received this email from a friend and would like to subscribe to our email list, please go to the following web address -<EMAIL_ADDRESS>To unsubscribe from the email list, please go to the following web address -<EMAIL_ADDRESS>J.Crew Customer Relations | One Ivy Crescent | Lynchburg, VA 24513-1001