| Interface | Description |
|---|---|
| AbstractUsersManager |
AbstractUsersManager tracks users in the system. |
| ConfigurationMutationACLPolicy |
Interface for determining whether configuration mutations are allowed.
|
| MutableConfigurationProvider |
Interface for allowing changing scheduler configurations.
|
| MutableConfScheduler |
Interface for a scheduler that supports changing configuration at runtime.
|
| NodeFilter |
Convenience way to filter nodes based on a criteria.
|
| PreemptableResourceScheduler |
Interface for a scheduler that supports preemption/killing
|
| Queue | |
| ResourceScheduler |
This interface is the one implemented by the schedulers.
|
| SchedulerQueue<T extends SchedulerQueue> |
Represents a queue in Scheduler.
|
| SchedulerQueueManager<T extends SchedulerQueue,E extends ReservationSchedulerConfiguration> |
Context of the Queues in Scheduler.
|
| YarnScheduler |
This interface is used by the components to talk to the
scheduler for allocating of resources, cleaning up resources.
|
| Class | Description |
|---|---|
| AbstractYarnScheduler<T extends SchedulerApplicationAttempt,N extends SchedulerNode> | |
| ActiveUsersManager |
ActiveUsersManager tracks active users in the system. |
| Allocation | |
| AppSchedulingInfo |
This class keeps track of all the consumption of an application.
|
| ClusterNodeTracker<N extends SchedulerNode> |
Helper library that:
- tracks the state of all cluster
SchedulerNode s
- provides convenience methods to filter and sort nodes |
| ConfigurationMutationACLPolicyFactory |
Factory class for creating instances of
ConfigurationMutationACLPolicy . |
| ContainerUpdateContext |
Class encapsulates all outstanding container increase and decrease
requests for an application.
|
| ContainerUpdates |
Holder class that maintains list of container update requests
|
| DefaultConfigurationMutationACLPolicy |
Default configuration mutation ACL policy.
|
| NodeReport |
Node usage report.
|
| NodeResponse |
The class that encapsulates response from clusterinfo for
updates from the node managers.
|
| QueueMetrics | |
| QueueStateManager<T extends SchedulerQueue,E extends ReservationSchedulerConfiguration> |
QueueStateManager which can be used by Scheduler to manage the queue state.
|
| ResourceLimits |
Resource limits for queues/applications, this means max overall (please note
that, it's not "extra") resource you can get.
|
| ResourceUsage |
Resource Usage by Labels for following fields by label - AM resource (to
enforce max-am-resource-by-label after YARN-2637) - Used resource (includes
AM resource usage) - Reserved resource - Pending resource - Headroom
This class can be used to track resource usage in queue/user/app.
|
| SchedContainerChangeRequest |
This is UpdateContainerRequest in scheduler side, it contains some
pointers to runtime objects like RMContainer, SchedulerNode, etc.
|
| SchedulerApplication<T extends SchedulerApplicationAttempt> | |
| SchedulerApplicationAttempt |
Represents an application attempt from the viewpoint of the scheduler.
|
| SchedulerAppReport |
Represents an application attempt, and the resources that the attempt is
using.
|
| SchedulerAppUtils | |
| SchedulerHealth | |
| SchedulerHealth.DetailedInformation | |
| SchedulerNode |
Represents a YARN Cluster Node from the viewpoint of the scheduler.
|
| SchedulerNodeReport |
Node usage report.
|
| SchedulerUtils |
Utilities shared by schedulers.
|
| Enum | Description |
|---|---|
| NodeType |
Resource classification.
|
| SchedulerApplicationAttempt.AMState |
Different state for Application Master, user can see this state from web UI
|
| Exception | Description |
|---|---|
| QueueInvalidException | |
| SchedulerDynamicEditException |
Copyright © 2018 Apache Software Foundation. All Rights Reserved.


OSS Licenses 101
- Copyleft VS
Copyright Non-copyleft
- Work VS Hobby
- Existing:
- Produce: choosealicense
Usage 3rd-party
commertial distribution + non-disclosure 😭
No
*unless OSS
- Compiled: GPL, MPL
- Network/Web: AGPL
Run / Saas service
*all non-EULA ofc
- All
free no restriction except AGPL
Produce
Library
- Do as in ecosystem!
- Compiled (for *.so): LGPG
- Network/Web: MIT (Rails, Express)
Product
*nginx, postgresql - BSD; gitlab-ce, wekan - MIT
- Compiled: GPL-3
- Network/Web: AGPL
- Mattermost, proxmox, lichess
- PeerTube, Diaspora, EdX, mastodon, ownCloud, Signal


The account link module will allow your customers to link their Facebook account with the Facebook application you have setup on your site.
Note: The account link module must be inserted within a secure zone. Customers must login in order for this module to render.
To insert this module, open the web page or template you would like to add this module to. Open the module manager, select Social media > Facebook Account link > Customize, select an image for Account Link/Unlink Image and then click Insert.
{module_facebookaccountlink, FbAccountLinkImg, FbAccountLinkText FbAccountUnlinkImg, FbAccountUnlinkText}


GDBUS-CODEGEN(1) User Commands GDBUS-CODEGEN(1) NAME gdbus-codegen - D-Bus code and documentation generator SYNOPSIS gdbus-codegen [--interface-prefix org.project.Prefix] [--generate-c-code OUTFILES] [--c-namespace YourProject] [--c-generate-object-manager] [--generate-docbook OUTFILES] [--annotate ELEMENT KEY VALUE]... FILE [FILE...] DESCRIPTION gdbus-codegen is used to generate code and/or documentation for one or more D-Bus interfaces. The tool reads D-Bus Introspection XML[1] files and generates output files. The tool currently supports generating C code (via --generate-c-code) and Docbook XML (via --generate-docbook). GENERATING C CODE When generating C code, a #GInterface -derived type is generated for each D-Bus interface. Additionally, for every generated type, FooBar, two concrete instantiable types, FooBarProxy and FooBarSkeleton, implementing said interface are also generated. The former is derived from #GDBusProxy and intended for use on the client side while the latter is derived from the #GDBusInterfaceSkeleton type making it easy to export on a #GDBusConnection either directly or via a #GDBusObjectManagerServer instance. The name of each generated C type is derived from the D-Bus interface name stripped with the prefix given with --interface-prefix and with the dots removed and initial characters capitalized. For example, for the D-Bus interface com.acme.Coyote the name used is ComAcmeCoyote. For the D-Bus interface org.project.Bar.Frobnicator with --interface-prefix org.project., the name used is BarFrobnicator. For methods, signals and properties, if not specified, the name defaults to the name of the method, signal or property. Two forms of the name are used - the CamelCase form and the lower-case form. The CamelCase form is used for the #GType and struct name, while lower-case form is used in function names. The lower-case form is calculated by converting from CamelCase to lower-case and inserting underscores at word boundaries (using certain heuristics). If the value given by the org.gtk.GDBus.C.Name annotation or the --c-namespace option contains an underscore (sometimes called Ugly_Case), then the camel-case name is derived by removing all underscores, and the lower-case name is derived by lower-casing the string. This is useful in some situations where abbreviations are used. For example, if the annotation is used on the interface net.MyCorp.MyApp.iSCSITarget with the value iSCSI_Target the CamelCase form is iSCSITarget while the lower-case form is iscsi_target. If the annotation is used on the method EjectTheiPod with the value Eject_The_iPod, the lower-case form is eject_the_ipod. GENERATING DOCBOOK DOCUMENTATION Each generated Docbook XML file (see the --generate-docbook option for details) is a RefEntry[2] article describing the D-Bus interface. OPTIONS The following options are supported: --interface-prefix org.project.Prefix. A prefix to strip from all D-Bus interface names when calculating the typename for the C binding and the Docbook sortas attribute[3]. --generate-docbook OUTFILES Generate Docbook Documentation for each D-Bus interface and put it in OUTFILES-NAME.xml where NAME is a place-holder for the interface name, e.g. net.Corp.FooBar and so on. --generate-c-code OUTFILES Generate C code for all D-Bus interfaces and put it in OUTFILES.c and OUTFILES.h. --c-namespace YourProject The namespace to use for generated C code. This is expected to be in CamelCase[4] or Ugly_Case (see above). --c-generate-object-manager If this option is passed, suitable #GDBusObject, #GDBusObjectProxy, #GDBusObjectSkeleton and #GDBusObjectManagerClient subclasses are generated. --annotate ELEMENT KEY VALUE Used to inject D-Bus annotations into the given XML files. It can be used with interfaces, methods, signals, properties and arguments in the following way: gdbus-codegen --c-namespace MyApp \ --generate-c-code myapp-generated \ --annotate "org.project.InterfaceName" \ org.gtk.GDBus.C.Name MyFrobnicator \ --annotate "org.project.InterfaceName:Property" \ bar bat \ --annotate "org.project.InterfaceName.Method()" \ org.freedesktop.DBus.Deprecated true \ --annotate "org.project.InterfaceName.Method()[arg_name]" \ snake hiss \ --annotate "org.project.InterfaceName::Signal" \ cat meow \ --annotate "org.project.InterfaceName::Signal[arg_name]" \ dog wuff \ myapp-dbus-interfaces.xml Any UTF-8 string can be used for KEY and VALUE. SUPPORTED D-BUS ANNOTATIONS The following D-Bus annotations are supported by gdbus-codegen: org.freedesktop.DBus.Deprecated Can be used on any <interface>, <method>, <signal> and <property> element to specify that the element is deprecated if its value is true. Note that this annotation is defined in the D-Bus specification[1] and can only assume the values true and false. In particular, you cannot specify the version that the element was deprecated in nor any helpful deprecation message. Such information should be added to the element documentation instead. When generating C code, this annotation is used to add #G_GNUC_DEPRECATED to generated functions for the element. When generating Docbook XML, a deprecation warning will appear along the documentation for the element. org.gtk.GDBus.Since Can be used on any <interface>, <method>, <signal> and <property> element to specify the version (any free-form string but compared using a version-aware sort function) the element appeared in. When generating C code, this field is used to ensure function pointer order for preserving ABI/API, see the section called “STABILITY GUARANTEES”. When generating Docbook XML, the value of this tag appears in the documentation. org.gtk.GDBus.DocString A string with Docbook content for documentation. This annotation can be used on <interface>, <method>, <signal>, <property> and <arg> elements. org.gtk.GDBus.DocString.Short A string with Docbook content for short/brief documentation. This annotation can only be used on <interface> elements. org.gtk.GDBus.C.Name Can be used on any <interface>, <method>, <signal> and <property> element to specify the name to use when generating C code. The value is expected to be in CamelCase[4] or Ugly_Case (see above). org.gtk.GDBus.C.ForceGVariant If set to a non-empty string, a #GVariant instance will be used instead of the natural C type. This annotation can be used on any <arg> and <property> element. org.gtk.GDBus.C.UnixFD If set to a non-empty string, the generated code will include parameters to exchange file descriptors using the #GUnixFDList type. This annotation can be used on <method> elements. As an easier alternative to using the org.gtk.GDBus.DocString annotation, note that parser used by gdbus-codegen parses XML comments in a way similar to gtk-doc[5]: Note that @since can be used in any inline documentation bit (e.g. for interfaces, methods, signals and properties) to set the org.gtk.GDBus.Since annotation. For the org.gtk.GDBus.DocString annotation (and inline comments), note that substrings of the form #net.Corp.Bar, net.Corp.Bar.FooMethod(), #net.Corp.Bar::BarSignal and #net.Corp.InlineDocs:BazProperty are all expanded to links to the respective interface, method, signal and property. Additionally, substrings starting with @ and % characters are rendered as parameter[6] and constant[7] respectively. If both XML comments and org.gtk.GDBus.DocString or org.gtk.GDBus.DocString.Short annotations are present, the latter wins. EXAMPLE Consider the following D-Bus Introspection XML. <node> <interface name="net.Corp.MyApp.Frobber"> <method name="HelloWorld"> <arg name="greeting" direction="in" type="s"/> <arg name="response" direction="out" type="s"/> </method> <signal name="Notification"> <arg name="icon_blob" type="ay"/> <arg name="height" type="i"/> <arg name="messages" type="as"/> </signal> <property name="Verbose" type="b" access="readwrite"/> </interface> </node> If gdbus-codegen is used on this file like this: gdbus-codegen --generate-c-code myapp-generated \ --c-namespace MyApp \ --interface-prefix net.corp.MyApp. \ net.Corp.MyApp.Frobber.xml two files called myapp-generated.[ch] are generated. The files provide an abstract #GTypeInterface -derived type called MyAppFrobber as well as two instantiable types with the same name but suffixed with Proxy and Skeleton. The generated file, roughly, contains the following facilities: /* GType macros for the three generated types */ #define MY_APP_TYPE_FROBBER (my_app_frobber_get_type ()) #define MY_APP_TYPE_FROBBER_SKELETON (my_app_frobber_skeleton_get_type ()) #define MY_APP_TYPE_FROBBER_PROXY (my_app_frobber_proxy_get_type ()) typedef struct _MyAppFrobber MyAppFrobber; /* Dummy typedef */ typedef struct { GTypeInterface parent_iface; /* Signal handler for the ::notification signal */ void (*notification) (MyAppFrobber *proxy, GVariant *icon_blob, gint height, const gchar* const *messages); /* Signal handler for the ::handle-hello-world signal */ gboolean (*handle_hello_world) (MyAppFrobber *proxy, GDBusMethodInvocation *invocation, const gchar *greeting); } MyAppFrobberIface; /* Asynchronously calls HelloWorld() */ void my_app_frobber_call_hello_world (MyAppFrobber *proxy, const gchar *greeting, GCancellable *cancellable, GAsyncReadyCallback callback, gpointer user_data); gboolean my_app_frobber_call_hello_world_finish (MyAppFrobber *proxy, gchar **out_response, GAsyncResult *res, GError **error); /* Synchronously calls HelloWorld(). Blocks calling thread. */ gboolean my_app_frobber_call_hello_world_sync (MyAppFrobber *proxy, const gchar *greeting, gchar **out_response, GCancellable *cancellable, GError **error); /* Completes handling the HelloWorld() method call */ void my_app_frobber_complete_hello_world (MyAppFrobber *object, GDBusMethodInvocation *invocation, const gchar *response); /* Emits the ::notification signal / Notification() D-Bus signal */ void my_app_frobber_emit_notification (MyAppFrobber *object, GVariant *icon_blob, gint height, const gchar* const *messages); /* Gets the :verbose GObject property / Verbose D-Bus property. * Does no blocking I/O. */ gboolean my_app_frobber_get_verbose (MyAppFrobber *object); /* Sets the :verbose GObject property / Verbose D-Bus property. * Does no blocking I/O. */ void my_app_frobber_set_verbose (MyAppFrobber *object, gboolean value); /* Gets the interface info */ GDBusInterfaceInfo *my_app_frobber_interface_info (void); /* Creates a new skeleton object, ready to be exported */ MyAppFrobber *my_app_frobber_skeleton_new (void); /* Client-side proxy constructors. * * Additionally, _new_for_bus(), _new_for_bus_finish() and * _new_for_bus_sync() proxy constructors are also generated. */ void my_app_frobber_proxy_new (GDBusConnection *connection, GDBusProxyFlags flags, const gchar *name, const gchar *object_path, GCancellable *cancellable, GAsyncReadyCallback callback, gpointer user_data); MyAppFrobber * my_app_frobber_proxy_new_finish (GAsyncResult *res, GError **error); MyAppFrobber * my_app_frobber_proxy_new_sync (GDBusConnection *connection, GDBusProxyFlags flags, const gchar *name, const gchar *object_path, GCancellable *cancellable, GError **error); Thus, for every D-Bus method, there will be three C functions for calling the method, one #GObject signal for handling an incoming call and one C function for completing an incoming call. For every D-Bus signal, there's one #GObject signal and one C function for emitting it. For every D-Bus property, two C functions are generated (one setter, one getter) and one #GObject property. The following table summarizes the generated facilities and where they are applicable: allbox tab(:); lB lB lB.  T{ Types T}:T{ Use MyAppFrobberProxy T}:T{ Any type implementing the MyAppFrobber interface T} T{ Methods T}:T{ Use m_a_f_hello_world() to call. T}:T{ Receive via the handle_hello_world() signal handler. Complete the call with m_a_f_complete_hello_world() T} T{ Signals T}:T{ Connect to the ::notification GObject signal. T}:T{ Use m_a_f_emit_notification() to emit signal. T} T{ Properties (Reading) T}:T{ Use m_a_f_get_verbose() or :verbose. T}:T{ Implement #GObject's get_property() vfunc. T} T{ Properties (writing) T}:T{ Use m_a_f_set_verbose() or :verbose. T}:T{ Implement #GObject's set_property() vfunc. T} Client-side usage You can use the generated proxy type with the generated constructors: MyAppFrobber *proxy; GError *error; error = NULL; proxy = my_app_frobber_proxy_new_for_bus_sync ( G_BUS_TYPE_SESSION, G_DBUS_PROXY_FLAGS_NONE, "net.Corp.MyApp", /* bus name */ "/net/Corp/MyApp/SomeFrobber", /* object */ NULL, /* GCancellable* */ &error); /* do stuff with proxy */ g_object_unref (proxy); Instead of using the generic #GDBusProxy facilities, one can use the generated methods such as my_app_frobber_call_hello_world() to invoke the net.Corp.MyApp.Frobber.HelloWorld() D-Bus method, connect to the the ::notification GObject signal to receive the net.Corp.MyApp.Frobber::Notication D-Bus signal and get/set the net.Corp.MyApp.Frobber:Verbose D-Bus Property using either the GObject property :verbose or the my_app_get_verbose() and my_app_set_verbose() methods. Use the standard #GObject::notify signal to listen to property changes. Note that all property access is via #GDBusProxy 's property cache so no I/O is ever done when reading properties. Also note that setting a property will cause the org.freedesktop.DBus.Properties.Set[8] method to be called on the remote object. This call, however, is asynchronous so setting a property won't block. Further, the change is delayed and no error checking is possible. Server-side usage The generated MyAppFrobber interface is designed so it is easy to implement it in a #GObject subclass. For example, to handle HelloWorld() method invocations, set the vfunc for handle_hello_hello_world() in the MyAppFrobberIface structure. Similary, to handle the net.Corp.MyApp.Frobber:Verbose property override the :verbose #GObject property from the subclass. To emit a signal, use e.g. my_app_emit_signal() or g_signal_emit_by_name(). Instead of subclassing, it is often easier to use the generated MyAppFrobberSkeleton subclass. To handle incoming method calls, use g_signal_connect() with the ::handle-* signals and instead of overriding #GObject 's get_property() and set_property() vfuncs, use g_object_get() and g_object_set() or the generated property getters and setters (the generated class has an internal property bag implementation). static gboolean on_handle_hello_world (MyAppFrobber *interface, GDBusMethodInvocation *invocation, const gchar *greeting, gpointer user_data) { if (g_strcmp0 (greeting, "Boo") != 0) { gchar *response; response = g_strdup_printf ("Word! You said `%s'.", greeting); my_app_complete_hello_world (interface, invocation, response); g_free (response); } else { g_dbus_method_invocation_return_error (invocation, MY_APP_ERROR, MY_APP_ERROR_NO_WHINING, "Hey, %s, there will be no whining!", g_dbus_method_invocation_get_sender (invocation)); } return TRUE; } [...] interface = my_app_frobber_skeleton_new (); my_app_frobber_set_verbose (interface, TRUE); g_signal_connect (interface, "handle-hello-world", G_CALLBACK (on_handle_hello_world), some_user_data); [...] error = NULL; if (!g_dbus_interface_skeleton_export (G_DBUS_INTERFACE_SKELETON (interface), connection, "/path/of/dbus_object", &error)) { /* handle error */ } To facilitate atomic changesets (multiple properties changing at the same time), #GObject::notify signals are queued up when received. The queue is drained in an idle handler (which is called from the thread-default main loop of the thread where the skeleton object was contructed) and will cause emissions of the org.freedesktop.DBus.Properties::PropertiesChanged[8] signal with all the properties that have changed. Use g_dbus_interface_skeleton_flush() or g_dbus_object_skeleton_flush() to empty the queue immediately. Use g_object_freeze_notify() and g_object_thaw_notify() for atomic changesets if on a different thread. C TYPE MAPPING Scalar types (type-strings and and and gchar*, gchar** and so on. Everything else is mapped to the #GVariant type. This automatic mapping can be turned off by using the annotation org.gtk.GDBus.C.ForceGVariant - if used then a #GVariant is always exchanged instead of the corresponding native C type. This annotation may be convenient to use when using bytestrings (type-string STABILITY GUARANTEES The generated C functions are guaranteed to not change their ABI that is, if a method, signal or property does not change its signature in the introspection XML, the generated C functions will not change its C ABI either. The ABI of the generated #GType s will be preserved only if the org.gtk.GDBus.Since annotation is used judiciously — this is because the VTable for the #GInterface relies on functions pointers for signal handlers. Specifically, if a D-Bus method, property or signal or is added to a D-Bus interface, then ABI of the generated #GInterface type is preserved if, and only if, each added method, property signal is annotated with they org.gtk.GDBus.Since annotation using a greater version number than previous versions. The generated C code currently happens to be annotated with gtk-doc[5] / GObject Introspection[9] comments / annotations. The layout and contents might change in the future so no guarantees about e.g. SECTION usage etc. is given. While the generated Docbook for D-Bus interfaces isn't expected to change, no guarantees are given at this point. AUTHOR Written by David Zeuthen<EMAIL_ADDRESS>with a lot of help from many others. BUGS Please send bug reports to either the distribution bug tracker or the upstream bug tracker at https://bugzilla.gnome.org/enter_bug.cgi?product=glib. SEE ALSO gdbus(1) NOTES 1. D-Bus Introspection XML http://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format 2. RefEntry http://www.docbook.org/tdg/en/html/refentry.html 3. sortas attribute http://www.docbook.org/tdg/en/html/primary.html 4. CamelCase http://en.wikipedia.org/wiki/CamelCase 5. gtk-doc http://www.gtk.org/gtk-doc/ 6. parameter http://www.docbook.org/tdg/en/html/parameter.html 7. constant http://www.docbook.org/tdg/en/html/constant.html 8. org.freedesktop.DBus.Properties.Set http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties 9. GObject Introspection https://live.gnome.org/GObjectIntrospection User Commands 07/14/2012 GDBUS-CODEGEN(1)


| Trees | Indices | Help |
|---|
|
|
object --+ | GenericJSONParser
Takes a JSON string, and returns a CSV row for later import into a relational database.
|
|||
|
|||
|
|||
|
|||
| List<<any>> |
|
||
|
|||
|
|||
| String |
|
||
|
|||
|
|||
|
|||
|
Inherited from |
|
|||
REMOVE_ITEM_FROM_STRING_PATTERN = re.compile(r'
|
|
|||
|
Inherited from |
|
x.__init__(...) initializes x; see help(type(x)) for signature
|
To be called after one row has been processed in processOneJSONObject() of this class or one of its subclasses. Cleans out any datastructures that are only good during creation of one row. |
Given a JSON string that is one entire JSON object, parse the string into nested dicts. Derive relational column names from the (possibly nested) labels. Cooperate with the parent JSONToRelations instance to build a schema of typed SQL columns. Fill the passed-in row with values from the JSON string. The following mappings from Python values are used: ('null', None) ('boolean', <true orfFalse>) ('number', <int or Decimal>) ('string', <unicode>) ('map_key', <str>) ('start_map', None) ('end_map', None) ('start_array', None) ('end_array', None) @param jsonStr: string of a single, self contained JSON object @type jsonStr: String @param row: partially filled array of values. @type row: List<<any>> @return: array of values. Fills into the passed-in row array @rtype: [<any>] |
Given a column name, a value and a partially filled row, add the column to the row, or set the value in an already existing row. Uses the JSONToRelation instance passed to __init__() to obtain current schema.
|
Given a label, like employee.item.name, remove the last occurrence of 'item'
|
|
REMOVE_ITEM_FROM_STRING_PATTERN
|
| Trees | Indices | Help |
|---|
| Generated by Epydoc 3.0.1 on Wed Oct 16 17:51:59 2013 | http://epydoc.sourceforge.net |


Assassin's Creed ® Revelations
When a man has won all of his battles and defeated all of his enemies, what is left for him to achieve?
Ezio Auditore must leave his life behind in search of answers, in search of the truth. In Assassin's Creed® Revelations, master assassin Ezio Auditore walks in the footsteps of the legendary mentor Altaïr, on a journey of discovery and revelation. It is a perilous path — one that will take Ezio to Constantinople, the heart of the Ottoman Empire, where a growing army of Templars threatens to destabilize the region.
!!! CLICK HERE FOR EXCLUSIVE GAMEPLAY TRAILERS !!!
KEY GAME FEATURES
- Fight as both Ezio and Altair to discover the truth behind the Creed. Walk in the footsteps of these master Assassins to uncover the secrets behind their Order and the destiny that unites them.
- Navigate your environment faster and more fluidly than ever with the new hookblade.
- Experience new levels of gameplay customization with advanced bomb crafting. Using components found throughout the vast world of Assassin’s Creed Revelations, you’ll be able to create hundreds of different bombs to serve a multitude of functions, perfectly tailoring each to suit your gameplay style.


News Flash
Login
Please enter your email and password.
Remember me
Login
Not a member yet? Sign up here!


--- layout: post title: Twisted view of Liège date: '2014-08-09T08:05:00+02:00' categories: - Illustration picture_url: https://film-Storyboards.tumblr.com/post/94244849481/twisted-view-of-liege ---


Kathy Huynh is a student at UC San Diego. She is a Visual Arts student with a passion for design. She has experience in visual and graphic design, photography, and illustration.


|
Timetable
|
Macros | |
| #define | _CRT_SECURE_NO_WARNINGS |
Functions | |
| void | deleteLines (lines **pHeadL, int NO) |
| void | deleteBustopFromLines (lines **pHeadL, int NO, char *name) |
| void | deleteBustopFromCity (lines **pHeadL, char *name, cities **pHeadC) |
| void | deleteAll (cities **pHeadC, lines **pHeadL) |
| #define _CRT_SECURE_NO_WARNINGS |
Function deletes all bus stops from cities
| void deleteBustopFromLines | ( | lines ** | pHeadL, |
| int | NO, | ||
| char * | name | ||
| ) |
Function deletes all bus stops from lines
| void deleteLines | ( | lines ** | pHeadL, |
| int | NO | ||
| ) |
Function deletes all lines from memory (structure)


| Name | Size | Last Modified | ||
|---|---|---|---|---|
|
5/14/2015 | 6:15:30 AM | ||
|
5/14/2015 | 5:16:49 AM | ||
|
1 KB | 5/28/2015 | 7:59:36 AM | |
|
5/24/2015 | 12:10:50 AM | ||
|
5/14/2015 | 6:15:30 AM | ||
|
5/28/2015 | 9:15:05 AM | ||
|
5/28/2015 | 9:13:58 AM | ||
|
5/23/2015 | 11:57:24 PM | ||
|
5/21/2015 | 9:34:17 PM | ||
|
237 KB | 11/7/2007 | 9:53:12 AM | |
|
1883 KB | 11/7/2007 | 9:50:40 AM | |
|
5/24/2015 | 12:39:03 AM | ||
|
12/31/1969 | 10:00:00 PM | ||
|
5/23/2015 | 3:29:39 AM | ||
|
5/7/2015 | 11:12:15 PM | ||
|
12/31/1969 | 10:00:00 PM | ||
|
12/31/1969 | 10:00:00 PM |


>UpSet About Page
If you are not redirected automatically, follow the
link to the latest version of the class


# File /usr/lib/ruby/gems/1.8/gems/activerecord-3.0.0.beta4/lib/active_record/serialization.rb, line 6 6: def serializable_hash(options = nil) 7: options ||= {} 8: 9: options[:except] = Array.wrap(options[:except]).map { |n| n.to_s } 10: options[:except] |= Array.wrap(self.class.inheritance_column) 11: 12: hash = super(options) 13: 14: serializable_add_includes(options) do |association, records, opts| 15: hash[association] = records.is_a?(Enumerable) ? 16: records.map { |r| r.serializable_hash(opts) } : 17: records.serializable_hash(opts) 18: end 19: 20: hash 21: end
Builds an XML document to represent the model. Some configuration is available through options. However more complicated cases should override ActiveRecord::Base#to_xml.
By default the generated XML document will include the processing instruction and all the object‘s attributes. For example:
<?xml version="1.0" encoding="UTF-8"?> <topic> <title>The First Topic</title> <author-name>David</author-name> <id type="integer">1</id> <approved type="boolean">false</approved> <replies-count type="integer">0</replies-count> <bonus-time type="datetime">2000-01-01T08:28:00+12:00</bonus-time> <written-on type="datetime">2003-07-16T09:28:00+1200</written-on> <content>Have a nice day</content><EMAIL_ADDRESS><parent-id></parent-id> <last-read type="date">2004-04-15</last-read> </topic>
This behavior can be controlled with :only, :except, :skip_instruct, :skip_types, :dasherize and :camelize . The :only and :except options are the same as for the attributes method. The default is to dasherize all column names, but you can disable this setting :dasherize to false. Setting :camelize to true will camelize all column names - this also overrides :dasherize. To not have the column type included in the XML output set :skip_types to true.
For instance:
topic.to_xml(:skip_instruct => true, :except => [ :id, :bonus_time, :written_on, :replies_count ]) <topic> <title>The First Topic</title> <author-name>David</author-name> <approved type="boolean">false</approved> <content>Have a nice day</content><EMAIL_ADDRESS><parent-id></parent-id> <last-read type="date">2004-04-15</last-read> </topic>
To include first level associations use :include:
firm.to_xml :include => [ :account, :clients ] <?xml version="1.0" encoding="UTF-8"?> <firm> <id type="integer">1</id> <rating type="integer">1</rating> <name>37signals</name> <clients type="array"> <client> <rating type="integer">1</rating> <name>Summit</name> </client> <client> <rating type="integer">1</rating> <name>Microsoft</name> </client> </clients> <account> <id type="integer">1</id> <credit-limit type="integer">50</credit-limit> </account> </firm>
Additionally, the record being serialized will be passed to a Proc‘s second parameter. This allows for ad hoc additions to the resultant document that incorporate the context of the record being serialized. And by leveraging the closure created by a Proc, to_xml can be used to add elements that normally fall outside of the scope of the model — for example, generating and appending URLs associated with models.
proc = Proc.new { |options, record| options[:builder].tag!('name-reverse', record.name.reverse) } firm.to_xml :procs => [ proc ] <firm> # ... normal attributes as shown above ... <name-reverse>slangis73</name-reverse> </firm>
To include deeper levels of associations pass a hash like this:
firm.to_xml :include => {:account => {}, :clients => {:include => :address}} <?xml version="1.0" encoding="UTF-8"?> <firm> <id type="integer">1</id> <rating type="integer">1</rating> <name>37signals</name> <clients type="array"> <client> <rating type="integer">1</rating> <name>Summit</name> <address> ... </address> </client> <client> <rating type="integer">1</rating> <name>Microsoft</name> <address> ... </address> </client> </clients> <account> <id type="integer">1</id> <credit-limit type="integer">50</credit-limit> </account> </firm>
To include any methods on the model being called use :methods:
firm.to_xml :methods => [ :calculated_earnings, :real_earnings ] <firm> # ... normal attributes as shown above ... <calculated-earnings>100000000000000000</calculated-earnings> <real-earnings>5</real-earnings> </firm>
To call any additional Procs use :procs. The Procs are passed a modified version of the options hash that was given to to_xml:
proc = Proc.new { |options| options[:builder].tag!('abc', 'def') } firm.to_xml :procs => [ proc ] <firm> # ... normal attributes as shown above ... <abc>def</abc> </firm>
Alternatively, you can yield the builder object as part of the to_xml call:
firm.to_xml do |xml| xml.creator do xml.first_name "David" xml.last_name "Heinemeier Hansson" end end <firm> # ... normal attributes as shown above ... <creator> <first_name>David</first_name> <last_name>Heinemeier Hansson</last_name> </creator> </firm>
As noted above, you may override to_xml in your ActiveRecord::Base subclasses to have complete control about what‘s generated. The general form of doing this is:
class IHaveMyOwnXML < ActiveRecord::Base def to_xml(options = {}) options[:indent] ||= 2 xml = options[:builder] ||= Builder::XmlMarkup.new(:indent => options[:indent]) xml.instruct! unless options[:skip_instruct] xml.level_one do xml.tag!(:second_level, 'content') end end end
# File /usr/lib/ruby/gems/1.8/gems/activerecord-3.0.0.beta4/lib/active_record/serializers/xml_serializer.rb, line 174 174: def to_xml(options = {}, &block) 175: XmlSerializer.new(self, options).serialize(&block) 176: end


Chose one of two models to simulate stormwater runoff and water quality, to create different conservation and development scenarios, and to compare human impacts of these scenarios.
{% for model_package in model_packages %}{{ model_package.description }}
{% endif %}


WHEN:
September 2018 - April 2019
WHAT:
Independent Study in Computer Science
WHERE:
University of British Columbia, BC, Canada
TOOLS:
- Affinity Diagramming
- Content Analysis
- Running Usability Studies
The Asynchronous VR Collaboration project is one of the ongoing HCI research projects within the Multimodal User Experience Lab. This research specifically seeks to identify how users utilize multimodal expressions, such as speech, body language and scene manipulation, when reviewing and creating VR recordings.
Special thanks to Dr. Dongwook Yoon, Dr. Cuong Nguyen and Kevin Chow!
September 2018
Transcriptions & Deictic Gestures Analysis
Assisted in performing post-task interview transcriptions.
Catalogued instances of deictic gesture use from video data, indicating the referent, appoximate distance of reference, and the keyword utilized.
October - December 2018
Thematic Content Analysis
Performed qualitative analysis using thematic coding techniques on post-task interview transcriptions. The analysis served to cross-validate results from other research assistants and to identify new concepts previously buried.
Identified 147 concepts, and aggregated them into 24 themes through multiple iterations.
January 2019
Conceptual Design
Extracted requirements from the content analysis to guide the conceptual design.
Using affinity diagramming, began brainstorming potential design techniques, drawing from design implications in collaborative VR research.
Continued ideation using tablet-drawn annotations superimposed on image stills.
Produced more thorough documentation on PROs and CONs for each potential design.
Narrowed down primary design directions, produced more detailed conceptual designs and storyboarded them.
February - March 2019
POC Development
I was responsible for implementing three of the four POC features into the existing system. They were:
- Collaborator Aware X-Ray Vision: renders the occluded avatar and any objects within the POV of the avatar.
- Animated Scene Transitions: animates the changes performed between the current timeline, and that of a selected recording's timeline (analogous to "git diff" or how you would see code changes on github).
- Proxemic Sensitive Teleportation: renders the avatar in its future anticipated space when the user attempts to perform a teleportation, and redirects the teleportation arc so that the user's position does not overlap with that of the avatar.
March - April 2019
Running Usability Studies
I ran a series of usability studies to assess our four POC features. Participants were asked to perform a set of tasks, once with and once without the assistance of the feature.
Conclusions:
My work has contributed to our paper Challenges and Design Considerations for Multimodal Asynchronous Collaboration in VR, which was accepted into ACM CSCW 2019!


{* start animate collapse stuff *} {* this has to be at the end! *} {* Md temp add because Ext. JS in UTS doesnt work *} {* end animate collapse stuff *}


--- layout: page title: Features permalink: /features/ class: features-page --- {% include doc-shortcut-tip.html %}
IntelliJ Rust, apart from basic lexer highlighting, also highlights resolved types, functions, variables (marking out mutable ones) and macros. All color schemes are customizable and we support both Default and Darcula themes out of the box.
Reformat Code Ctrl+Alt+L reformats current file or selection using our custom, fully functional formatter based on IntelliJ's formatting engine. There's also a special action for formatting code with rustfmt.
To select a block of code place a cursor inside block and press Ctrl+W to expand it to an expression, to a line, to a logical block of code, and so on. To shrink selection press Ctrl+Shift+W as many times as needed.
After selecting a block, you can apply a block comment (Ctrl+Shift+/) or line comment (Ctrl+/) to it. The same shortcuts will remove existing comments from selected lines too.
Code folding, auto-insertion of braces, brackets & quotes, matching brace/bracket highlighting, etc.
Errors are shown as you type. Among others, we catch syntax errors, missing fields/methods and unnecessary parens. We also support IntelliJ's built-in spell-checker.
IntelliJ Rust features built from scratch code completion, leveraging IntelliJ Platform capabilities.
Ctrl+Space invokes completion. We do not plan
to use racer
. Most of the code completion is implemented, but support
for macros is a work in progress.
Remember, if the smart completion does not work for your particular case, you can always invoke "dumb completion" via Alt+/. It merely suggests identifiers already present in the file, but works surprisingly well.
There are a number of actions for efficient navigation across your project and dependencies.
Alt+F7 finds usages of element at caret.
Ctrl+B goes to the definition of the symbol at caret.
Ctrl+N search for a struct or enum by name.
Ctrl+Shift+Alt+N searches for any symbol (types, methods, functions, fields) by name. Together with Ctrl+N it is the main method to explore large projects.
Ctrl+U navigates to the parent module.
Ctrl+F12, Alt+7 brings up an overview of the current file.
Gutter icon or Ctrl+Alt+B shortcut can be used to navigate between traits or types and impls.
There is a number of built in live templates and you can define your own. Different live templates are available in different contexts. Use Ctrl+J to list templates available in context.
p, pd, ppd - println!
value with {}
, debug
{:?}
and pretty debug {:#?}
formats.
a, ae - assert!
/ assert_eq!
tfn - test function boilerplate
tmod - test module boilerplate
f, pf - (pub
) field name and type, applicable inside struct
definitions.
loop, while, for templates. You can select a fragment of code and press Ctrl+Alt+J to invoke Surround With Live Template action.
Expand module: invoke this refactoring inside foo.rs
file to get
foo/mod.rs
. Also available as a quick fix for unresolved module declaration.
Introduce variable: use Ctrl+Alt+V or .let
postfix template to extract a variable from an expression.
Intentions and quick fixes are micro refactorings automatically available depending on the context. If some intentions are available, a light bulb icon appears in the editor. You can use Alt+Enter to invoke a quick fix.
Contract module: the opposite of Expand Module refactoring. Available only if there are no child modules.
Create module file: if you have mod foo;
, but no foo.rs
this quick fix will create the missing file.
Extract inline module: move mod foo { ... }
to a separate file.
Add derive clause: adds #[derive(..)]
attribute to structs and enums.
Remove/Add curly braces: toggles between use foo::{bar}
and
use foo::bar
.
Add missing fields: a handy way to fill out the struct literal template.
Implement methods: quickly scafold an impl.
IntelliJ Rust highlights important parts of documentation comments, so they never look so bland.
Ctrl+Q shows docs for the symbol at caret.
Ctrl+Q shows docs for the symbol at caret.
IntelliJ Rust highlights important parts of documentation comments, so they never look so bland.
In the editor, you can see hints with names of parameters and types of local variables
Use Ctrl+Shift+P to view the type of selected expression.
Built-in Cargo Command
run configuration allows to build,
test and run Rust code.
main
or a test
function.
Alternatively, you can use the icon in the gutter area.


Raspberry Pi camera board video streaming
So you got your Raspberry Pi and decided to get a Camera Board to do something awesome with it. Why not turn it a simple video streamer? That's what I thought too. I wanted to set up a simple security camera for my home so that I can see spy on whoever is lurking around from wherever I am through a web browser. Turns out it wasn't hard at all to set up. This blog post helped me get started. I'm going to walk you through all the steps I took.
Installing Raspbian
I want to point out that I am using the Debian based Raspbian operating system. I followed this article on how to make the bootable SD card. Basically all I did was download the Raspbian img, unmount the SD card, and ran the dd
command (on Ubuntu).
# List the mounted media devices.
df -h
# Unmount SD card to be able to write the img on to it.
# Important that you make sure you are unmounting the correct device.
umount /dev/sdd1
# Now write the img file.
# Adjust the input file path to your own.
# VERY IMPORTANT that the output path is pointing to your SD card.
# If not set correctly it can possibly corrupt your hard drive.
sudo dd bs=4M if=~/Downloads/2013-05-25-wheezy-raspbian.img of=/dev/sdd
# Be patient. It might take a minute or two to copy the Raspbian img on the SD card.
Installing MJPG Streamer
After booting up your Raspberry Pi, install MJPG Streamer.
# Make and change into directory.
sudo mkdir /opt/mjpg-streamer
cd /opt/mjpg-streamer/
# Install the following packages.
sudo apt-get install libjpeg8-dev
sudo apt-get install imagemagick
sudo apt-get install subversion
# Download MJPG Streamer into the current directory.
sudo svn co https://svn.code.sf.net/p/mjpg-streamer/code/mjpg-streamer/ .
# Run make.
sudo make
If you get the following error:
linux/videodev.h: No such file or directory
Make sure you have libv4l-dev
installed and create a symbolic link for the header file:
sudo apt-get install libv4l-dev
sudo ln -s /usr/include/libv4l1-videodev.h /usr/include/linux/videodev.h
Start capturing
Alright now for the fun part. Streaming the video.
# Make a directory to store the temporary images.
sudo mkdir /tmp/stream/
# Make the directory writable.
sudo chmod a+rw /tmp/stream/
# Start capturing.
# See what the raspistill options are.
raspistill --help
# You see the record light turn on after executing the following line.
raspistill -w 640 -h 480 -q 5 -o /tmp/stream/pic.jpg -tl 100 -t 9999999 -th 0:0:0 -n &
# See what the MJPG Streamer options are.
/opt/mjpg-streamer/mjpg_streamer --help
# Run the following to start up the MJPG Streamer streaming webserver.
LD_LIBRARY_PATH=/opt/mjpg-streamer/ /opt/mjpg-streamer/mjpg_streamer -i "input_file.so -f /tmp/stream -n pic.jpg" -o "output_http.so -p 9000 -w /opt/mjpg-streamer/www" &
If everything went smoothly you can open up a web browser and go to:
http://<your-raspberry-pi-ip-address>:9000/
There you have it. To access your streaming webserver remotely you will need to enable port forwarding on your router. Since every router is different I can't explain how, but the PortForward site can guide you.
Stopping stream
To stop capturing and turn of the webserver we must kill the raspistill
and mjpg
processes that are running in the background.
 I hope this tutorial helped you get started with simple video streaming on the Raspberry Pi using the awesome camera board module. Leave a comment if this post was useful or not. There is always room for improvement.
Update: 19 Jan 2014 - Easier way to stream
I stumbled upon this fork of MJPG Streamer on github which comes with the raspicam input plugin. Using this version of MJPG Streamer we can skip dealing with raspistill and let the raspicam plugin take care of creating the images. Here's how to install it.
# Install dev version of libjpeg
sudo apt-get install libjpeg62-dev
# Install cmake
sudo apt-get install cmake
# Download mjpg-streamer with raspicam plugin
git clone https://github.com/jacksonliam/mjpg-streamer.git ~/mjpg-streamer
# Change directory
cd ~/mjpg-streamer/mjpg-streamer-experimental
# Compile
make clean all
# Replace old mjpg-streamer
sudo rm -rf /opt/mjpg-streamer
sudo mv ~/mjpg-streamer/mjpg-streamer-experimental /opt/mjpg-streamer
sudo rm -rf ~/mjpg-streamer
# Begin streaming
LD_LIBRARY_PATH=/opt/mjpg-streamer/ /opt/mjpg-streamer/mjpg_streamer -i "input_raspicam.so -fps 15 -q 50 -x 640 -y 480" -o "output_http.so -p 9000 -w /opt/mjpg-streamer/www" &
Updated start/stop bash scripts (gist).
start_steam.sh
:
#!/bin/bash
if pgrep mjpg_streamer > /dev/null
then
echo "mjpg_streamer already running"
else
LD_LIBRARY_PATH=/opt/mjpg-streamer/ /opt/mjpg-streamer/mjpg_streamer -i "input_raspicam.so -fps 15 -q 50 -x 640 -y 480" -o "output_http.so -p 9000 -w /opt/mjpg-streamer/www" > /dev/null 2>&1&
echo "mjpg_streamer started"
fi
stop_stream.sh
:
#!/bin/bash
if pgrep mjpg_streamer
then
kill $(pgrep mjpg_streamer) > /dev/null 2>&1
echo "mjpg_streamer stopped"
else
echo "mjpg_streamer not running"
fi
I found this solution to work much more smoother than what I previously posted. Here's a short Vine video showing it in action.


March notes I.
25 Mar 2019First half of the March 2019 notes.
Mimosa in Jardin des Plantes.
Tverberg’s theorem
For geometric algorithms in the plane, one sometimes has go through case by case analysis along the lines of “if this point is below this line, then this and that intersect, if not then…”. Such proofs are a bit boring and it is easy to make mistakes. So when you have a general theorem that does the work for you, it’s good news. Tverberg’s theorem looks like a theorem that could be useful from this point of view.
Tverberg’s theorem states a condition such that the convex hulls of several sets of points intersect. Precisely: in a $d$-dimensional euclidian space, for any integer $r$, for any set of $(d+1)(r-1)+1$ points, there exists a partition in $r$ subsets such that the convex hulls of the $r$ subsets intersect. The picture below present the case $d=2$ and $r=3$, for $(d+1)(r-1)+1=7$ points, and for one less point. In this last case the theorem does not hold (we just show one partition).
[I saw the name of this theorem on the SOCG accepted papers list, unfortunately the paper is not available online, and we don’t know what they do with this theorem.]
Criteria for fair item assignment
Fair item assignement consists, given items and participants, to assign the items to the participants in a fair manner, for some definition of fair. There are many variants of the problem and many ways to define fairness.
Here are a few fairness criteria, to decide if the assignment is fair or not:
- Max-min fair-share (“I cut, you choose”): every participant is least as happy as if she had cut the set of items first, and then let all the other participants choose before her.
- Max-min fair-share (“You cut, I choose”): the same but reversed, that is every participant is at least as happy as if someone else did the cut, and she could decide first.
- Envy-freeness: no participant would like to change her items for the items of another participant.
- Competitive equilibrium from equal incomes: there exists a price for each item such that, given the same budget, the participants would choose different items.
[I learnt about this at the CS PhD seminar of Sorbonne university, by Parham Shams.]
Tai chi problem
When crossing the Jardin des plantes I often witness the following kind of scene.
It is people practising taichi. There is a professor in front of the group (with a white cap on the picture) who is showing the movements, and everybody is supposed to perform them in real-time (it’s pretty slow).
The thing is: people on the first row can see the professor, but the ones on the back cannot, so they follow the moves of the people on the rows closer to the professor. Therefore there is a kind of wave from the front to the back. Maybe it can make an interesting problem: how fast does the wave propagate, is it close to a straight line, how does it depend on the size of the participants?
Core algorithms deployed
It is common as a reseacher to have doubt about how useful your research is. In my case, I sometimes wonder whether the algorithmic problem we try to solve really have an impact. It could well be the case that the algorithmic problems that are really useful are the ones that have only basic answers. That is, we focus on the sweet spot between trivially easy and trivially hard problems, and this set could have an empty intersection with real-world questions.
I was really happy to discover a few years ago the topic “core algorithms deployed” on stack exchange, that removes any doubt on this regard.
Numerical errors in missile trajectories
I discovered in the introduction of this PhD thesis the following story, illustrating why computer arithmetics is important and difficult.
In 2011, a US “defence missile” missed a “real missile”, with tragic consequences, because of computer arithmetic. The basic reason is the following. There used to be a software doing the trajectory computations, with rounding operations, including on the time variable. This variable slowly shifted compared to the real time because of these rounding. It sounds dangerous, but it was actually ok: the trajectory computations would consider fast movements so between the start and end of the trajectory, the shift was negligible, and the absolute time did not matter. The problem is that part of the system was updated with more accurate time variable. Then the shift would not be the same in two different parts of the system. Then the shift would not cancel out and this was the bug.
[A better explanation can be found in this document. The PhD thesis has a more light-hearted story about gamers trying to finish a video game level without jumping, and using a slow shift of a platform (also due to rounding errors) to do so.]
Max cut and planar graphs
Two results about max-cut that I didn’t know:
-
a cut is maximum if and only if its complement is a minimum odd-circuit cover (this is easy to check, see for example here, or simply stare a bit at the picture below.)
-
This can be used to obtain a polynomial-time algorithm for max-cut in planar graphs.
[I got aware of this by this preprint which presents an algorithm for max-cut whose complexity is parametrized by the number of crossing in the drawing of the graph.]


Source code for matchernet.fn
"""
fn.py
=====
This module contains function handler classes that the BundleNet
architecture needs. It is overridden when you use chainer/TensorFlow to implement the arbitrary parametric functions.
"""
import autograd.numpy as np
from autograd import jacobian
[docs]class Fn(object):
"""An abstract class to implement numerical function
that BundleNet uses.
"""
def __init__(self, A):
self.A = A
self.x = jacobian(self.value, 0)
[docs] def get_params(self):
return self.A
[docs] def value(self, x):
"""Numerically calculates f(x)
x should be a numpy array of shape (dim_in, 1)
outputs a numpy array of shape (dim_out, 1)
"""
return 0
[docs]class LinearFn(Fn):
"""Linear function y = np.dot(A, x) and its derivatives.
"""
def __init__(self, A):
super(LinearFn, self).__init__(A)
self.A = A
self.dx = jacobian(self.value, 0)
[docs] def value(self, x):
return np.dot(self.A, x)
[docs]class LinearFnXU(object):
"""Linear function y = np.dot(A, x) + np.dot(B, u) and its derivatives.
.. note:: The shapes of matrix A and matrix B must match
"""
def __init__(self, A, B):
self.A = A
self.B = B
self.dx = jacobian(self.value, 0)
self.du = jacobian(self.value, 1)
[docs] def value(self, x, u):
return np.dot(self.A, x) + np.dot(self.B, u)


Visualise clustering algorithms with GGobi. Contains both general code for visualising clustering results and specific visualisations for model-based, hierarchical and SOM clustering.
| Version: | 0.4 |
| Depends: | rggobi |
| Imports: | e1071, reshape2, plyr, RGtk2 |
| Suggests: | som, mclust, kohonen, ggplot2 |
| Published: | 2014-04-24 |
| Author: | Hadley Wickham |
| Maintainer: | Hadley Wickham <h.wickham at gmail.com> |
| License: | MIT + file LICENSE |
| URL: | http://had.co.nz/clusterfly |
| NeedsCompilation: | no |
| Materials: | NEWS ChangeLog |
| In views: | Cluster |
| CRAN checks: | clusterfly results |
| Reference manual: | clusterfly.pdf |
| Package source: | clusterfly_0.4.tar.gz |
| Windows binaries: | r-devel: clusterfly_0.4.zip, r-release: clusterfly_0.4.zip, r-oldrel: clusterfly_0.4.zip |
| OS X binaries: | r-release: not available, r-oldrel: not available |
| Old sources: | clusterfly archive |
Please use the canonical form https://CRAN.R-project.org/package=clusterfly to link to this page.


Deputies search for missing SC teen who may be endangered
by Live 5 Web StaffWILLIAMSTON, S.C. (WCSC) - The Anderson County Sheriff’s Office is searching for a missing 16-year-old girl who deputies fear could hurt herself.
Ashlynn Owen was reported as a runaway to the Anderson County Sheriff’s Office on Friday, according to a post from the agency’s Facebook page.
She was last seen at her home in Williamston.
The post states she suffers from severe depression and may be suicidal.
She is 5-foot-7, weighs 120 pounds, and has blue eyes. The sheriff’s office updated her description to state that she has bright pink hair and blue eyes. She also has a tattoo on her lower right forearm that reads, “Forever.”
Anyone with information on Owen’s whereabouts is asked to please call the Anderson County Sheriff’s Office at<PHONE_NUMBER>. They ask that you provide case number 2019-17726.


Full-Stack Web Development
Design & Architecture. Responsive components. Logistical programming.
Database creation & maintenance. Server side programming. User authentication. Application security.
Ready to start your next project? That's great! Send me an email and I will get back to you as soon as possible!


--- # Feel free to add content and custom Front Matter to this file. # To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults layout: splash permalink: / header: overlay_color: "#013" overlay_filter: "0.25" overlay_image: /assets/images/TruDevBanner.png # caption: "" actions: - label: "Buy Copy Kitty! (not mine, but it's worth it!)" url: https://store.steampowered.com/app/349250/Copy_Kitty/ intro: - excerpt: "Welcome to my site! This is where I will post most of my progress." --- {% include feature_row id="intro" type="center" %}