You can create and edit user accounts through the
Admin Users
section.
Lets create a couple of user accounts.
- Press New User
- In the form specify the user information. For this exercise
specify "user1" as the ID. Under Roles specify "test". Specify a
easily remembered password for this exercise.
- You can optionally create a new Folder that the user
will own. Select the People folder.
- If you had email enabled for your RAMADDA you can also choose to send an
email with the login information.
- Press "Create User"
From the main user list you can view their activity () or
edit their account settings (img src="images/edit.png">)
Edit your new user1 account.


| Package | com.whirled.contrib.card |
| Class | public class HandEvent |
| Inheritance | HandEvent flash.events.Event |
| Property | Defined by | ||
|---|---|---|---|
| cards : CardArray
[read-only] The cards that have been dealt or passed.
| HandEvent | ||
| count : int [read-only] The number of cards requested to be passed.
| HandEvent | ||
| player : int [read-only] The player that passed or requested to pass the cards.
| HandEvent | ||
| targetPlayer : int [read-only] The player that is being passed to.
| HandEvent |
| Property | Defined by | ||
|---|---|---|---|
| _cards : CardArray | HandEvent | ||
| _count : int | HandEvent | ||
| _player : int | HandEvent | ||
| _targetPlayer : int | HandEvent |
| Method | Defined by | ||
|---|---|---|---|
|
Create a new HandEvent.
| HandEvent | ||
|
clone():Event
| HandEvent | ||
|
toString():String
| HandEvent |
| Constant | Defined by | ||
|---|---|---|---|
| ALLOWED_PLAY : String = "hand.allowedPlay" [static] The type of event when it is the player's turn.
| HandEvent | ||
| ALLOWED_SELECTION : String = "hand.allowedSelection" [static] The type of event when the local player may choose some cards, but not yet play them's turn.
| HandEvent | ||
| CARDS_PLAYED : String = "hand.played" [static] The type of event sent when cards have been selected for play.
| HandEvent | ||
| DEALT : String = "hand.dealt" [static] The type of event when the hand is dealt.
| HandEvent | ||
| DISALLOWED_SELECTION : String = "hand.disallowedSelection" [static] The type of event sent when the local player can no longer select or play any cards.
| HandEvent | ||
| PASSED : String = "hand.passed" [static] The type of event when cards are passed to the hand from another player.
| HandEvent | ||
| PASS_REQUESTED : String = "hand.requested" [static] The type of event when the rules of the game require the local player to pass cards.
| HandEvent |
| _cards | property |
protected var _cards:CardArray
| cards | property |
cards:CardArray
[read-only]The cards that have been dealt or passed.
Implementation public function get cards():CardArray
| _count | property |
protected var _count:int
| count | property |
count:int
[read-only]The number of cards requested to be passed.
Implementation public function get count():int
| _player | property |
protected var _player:int
| player | property |
player:int
[read-only]The player that passed or requested to pass the cards.
Implementation public function get player():int
| _targetPlayer | property |
protected var _targetPlayer:int
| targetPlayer | property |
targetPlayer:int
[read-only]The player that is being passed to.
Implementation public function get targetPlayer():int
| HandEvent | () | constructor |
public function HandEvent(type:String, cards:CardArray = null, player:int = 0, count:int = 0, targetPlayer:int = 0)
Create a new HandEvent.
Parameterstype:String |
|
cards:CardArray (default = null )
|
|
player:int (default = 0 )
|
|
count:int (default = 0 )
|
|
targetPlayer:int (default = 0 )
|
| clone | () | method |
public override function clone():Event
Returns
Event |
| toString | () | method |
public override function toString():String
Returns
String |
| ALLOWED_PLAY | constant |
public static const ALLOWED_PLAY:String = "hand.allowedPlay"
The type of event when it is the player's turn. For this event, the cards property is set to the set of cards that are allowed according to the game rules and the count property is set to the number of cards that should be played. The player and targetPlayer properties are not used.
| ALLOWED_SELECTION | constant |
public static const ALLOWED_SELECTION:String = "hand.allowedSelection"
The type of event when the local player may choose some cards, but not yet play them's turn. For this event, the cards property is set to the set of cards that are allowed to be selected (according to the game rules or game presentation) and the count property is set to the number of cards that may be selected. The player and targetPlayer properties are not used.
| CARDS_PLAYED | constant |
public static const CARDS_PLAYED:String = "hand.played"
The type of event sent when cards have been selected for play. For this event, the cards property indicates the selected ones and the other properties are not used.
| DEALT | constant |
public static const DEALT:String = "hand.dealt"
The type of event when the hand is dealt. For this event, the cards property is the new contents of the hand and the player, count and targetPlayer properties are not used.
| DISALLOWED_SELECTION | constant |
public static const DISALLOWED_SELECTION:String = "hand.disallowedSelection"
The type of event sent when the local player can no longer select or play any cards. For this event, no properties are used.
| PASSED | constant |
public static const PASSED:String = "hand.passed"
The type of event when cards are passed to the hand from another player. For this event, the cards property is the passed cards (if available), the player is the id of the player who has passed them, the count property is the number of cards passed and the targetPlayer is the id of the player receiving the passed cards.
| PASS_REQUESTED | constant |
public static const PASS_REQUESTED:String = "hand.requested"
The type of event when the rules of the game require the local player to pass cards. For this event type, the cards property is not used, the player property is the id of the player who is required to pass, the count property is the number of cards that should be passed and the targetPlayer is the player who will receive the passed cards.


Check your answers
Company’s activities and impact
Change
Consultation with stakeholders
Change
Directors' remuneration
Change
Assets transferred
Change


Actions, resources, and condition keys for Amazon Security Lake
Amazon Security Lake (service prefix:
securitylake
) provides the following service-specific resources, actions, and condition context keys for use in IAM permission policies.
References:
-
Learn how to configure this service .
-
View a list of the API operations available for this service .
-
Learn how to secure this service and its resources by using IAM permission policies.
Topics
Actions defined by Amazon Security Lake
You can specify the following actions in the
Action
element of an IAM policy statement. Use policies to grant permissions to perform an operation in AWS. When you use an action in a policy, you usually allow or deny access to the API operation or CLI command with the same name. However, in some cases, a single action controls access to more than one operation. Alternatively, some operations require several different actions.
The
Resource types
column of the Actions table indicates whether each action supports resource-level permissions. If there is no value for this column, you must specify all resources ("*") to which the policy applies in the
Resource
element of your policy statement. If the column includes a resource type, then you can specify an ARN of that type in a statement with that action. If the action has one or more required resources, the caller must have permission to use the action with those resources. Required resources are indicated in the table with an asterisk (*). If you limit resource access with the
Resource
element in an IAM policy, you must include an ARN or pattern for each required resource type. Some actions support multiple resource types. If the resource type is optional (not indicated as required), then you can choose to use one of the optional resource types.
The
Condition keys
column of the Actions table includes keys that you can specify in a policy statement's
Condition
element. For more information on the condition keys that are associated with resources for the service, see the
Condition keys
column of the Resource types table.
For details about the columns in the following table, see Actions table .
| Actions | Description | Access level | Resource types (*required) | Condition keys | Dependent actions |
|---|---|---|---|---|---|
| CreateAwsLogSource | Grants permission to enable any source type in any region for accounts that are either part of a trusted organization or standalone account | Write |
glue:CreateDatabase glue:CreateTable glue:GetDatabase glue:GetTable iam:CreateServiceLinkedRole kms:CreateGrant kms:DescribeKey |
||
| CreateCustomLogSource | Grants permission to add a custom source | Write |
glue:CreateCrawler glue:CreateDatabase glue:CreateTable glue:StartCrawlerSchedule iam:DeleteRolePolicy iam:GetRole iam:PassRole iam:PutRolePolicy kms:CreateGrant kms:DescribeKey kms:GenerateDataKey lakeformation:GrantPermissions lakeformation:RegisterResource s3:ListBucket s3:PutObject |
||
| CreateDataLake | Grants permission to create a new security data lake | Write |
events:PutRule events:PutTargets iam:CreateServiceLinkedRole iam:DeleteRolePolicy iam:GetRole iam:PassRole iam:PutRolePolicy kms:CreateGrant kms:DescribeKey lakeformation:GetDataLakeSettings lakeformation:PutDataLakeSettings lambda:CreateEventSourceMapping lambda:CreateFunction organizations:DescribeOrganization organizations:ListAccounts organizations:ListDelegatedServicesForAccount s3:CreateBucket s3:ListBucket s3:PutBucketPolicy s3:PutBucketPublicAccessBlock s3:PutBucketVersioning sqs:CreateQueue sqs:GetQueueAttributes sqs:SetQueueAttributes |
||
| CreateDataLakeExceptionSubscription | Grants permission to get instant notifications about exceptions. Subscribes to the SNS topics for exception notifications | Write | |||
| CreateDataLakeOrganizationConfiguration | Grants permission to automatically enable Amazon Security Lake for new member accounts in your organization | Write | |||
| CreateSubscriber | Grants permission to create a subscriber | Write |
iam:CreateRole iam:DeleteRolePolicy iam:GetRole iam:PutRolePolicy lakeformation:GrantPermissions lakeformation:ListPermissions lakeformation:RegisterResource lakeformation:RevokePermissions ram:GetResourceShareAssociations ram:GetResourceShares ram:UpdateResourceShare s3:PutObject |
||
| CreateSubscriberNotification | Grants permission to create a webhook invocation to notify a client when there is new data in the data lake | Write |
events:CreateApiDestination events:CreateConnection events:DescribeRule events:ListApiDestinations events:ListConnections events:PutRule events:PutTargets iam:DeleteRolePolicy iam:GetRole iam:PassRole s3:GetBucketNotification s3:PutBucketNotification sqs:CreateQueue sqs:DeleteQueue sqs:GetQueueAttributes sqs:GetQueueUrl sqs:SetQueueAttributes |
||
| DeleteAwsLogSource | Grants permission to disable any source type in any region for accounts that are part of a trusted organization or standalone accounts | Write | |||
| DeleteCustomLogSource | Grants permission to remove a custom source | Write |
glue:StopCrawlerSchedule |
||
| DeleteDataLake | Grants permission to delete security data lake | Write |
organizations:DescribeOrganization organizations:ListDelegatedAdministrators organizations:ListDelegatedServicesForAccount |
||
| DeleteDataLakeExceptionSubscription | Grants permission to unsubscribe from SNS topics for exception notifications. Removes exception notifications for the SNS topic | Write | |||
| DeleteDataLakeOrganizationConfiguration | Grants permission to remove the automatic enablement of Amazon Security Lake access for new organization accounts | Write | |||
| DeleteSubscriber | Grants permission to delete the specified subscriber | Write |
events:DeleteApiDestination events:DeleteConnection events:DeleteRule events:DescribeRule events:ListApiDestinations events:ListTargetsByRule events:RemoveTargets iam:DeleteRole iam:DeleteRolePolicy iam:GetRole iam:ListRolePolicies lakeformation:ListPermissions lakeformation:RevokePermissions sqs:DeleteQueue sqs:GetQueueUrl |
||
| DeleteSubscriberNotification | Grants permission to remove a webhook invocation to notify a client when there is new data in the data lake | Write |
events:DeleteApiDestination events:DeleteConnection events:DeleteRule events:DescribeRule events:ListApiDestinations events:ListTargetsByRule events:RemoveTargets iam:DeleteRole iam:DeleteRolePolicy iam:GetRole iam:ListRolePolicies lakeformation:RevokePermissions sqs:DeleteQueue sqs:GetQueueUrl |
||
| DeregisterDataLakeDelegatedAdministrator | Grants permission to remove the Delegated Administrator account and disable Amazon Security Lake as a service for this organization | Write |
organizations:DeregisterDelegatedAdministrator organizations:DescribeOrganization organizations:ListDelegatedServicesForAccount |
||
| GetDataLakeExceptionSubscription | Grants permission to query the protocol and endpoint that were provided when subscribing to SNS topics for exception notifications | Read | |||
| GetDataLakeOrganizationConfiguration | Grants permission to get an organization’s configuration setting for automatically enabling Amazon Security Lake access for new organization accounts | Read |
organizations:DescribeOrganization |
||
| GetDataLakeSources | Grants permission to get a static snapshot of the security data lake in the current region. The snapshot includes enabled accounts and log sources | Read | |||
| GetSubscriber | Grants permission to get information about subscriber that is already created | Read | |||
| ListDataLakeExceptions | Grants permission to get the list of all non-retryable failures | List | |||
| ListDataLakes | Grants permission to list information about the security data lakes | List | |||
| ListLogSources | Grants permission to view the enabled accounts. You can view the enabled sources in the enabled regions | List | |||
| ListSubscribers | Grants permission to list all subscribers | List | |||
| ListTagsForResource | Grants permission to list all tags for the resource | List | |||
| RegisterDataLakeDelegatedAdministrator | Grants permission to designate an account as the Amazon Security Lake administrator account for the organization | Write |
iam:CreateServiceLinkedRole organizations:DescribeOrganization organizations:EnableAWSServiceAccess organizations:ListDelegatedAdministrators organizations:ListDelegatedServicesForAccount organizations:RegisterDelegatedAdministrator |
||
| TagResource | Grants permission to add tags to the resource | Tagging | |||
| UntagResource | Grants permission to remove tags from the resource | Tagging | |||
| UpdateDataLake | Grants permission to update a security data lake | Write |
events:PutRule events:PutTargets iam:CreateServiceLinkedRole iam:DeleteRolePolicy iam:GetRole iam:PutRolePolicy kms:CreateGrant kms:DescribeKey lakeformation:GetDataLakeSettings lakeformation:PutDataLakeSettings lambda:CreateEventSourceMapping lambda:CreateFunction organizations:DescribeOrganization organizations:ListDelegatedServicesForAccount s3:CreateBucket s3:ListBucket s3:PutBucketPolicy s3:PutBucketPublicAccessBlock s3:PutBucketVersioning sqs:CreateQueue sqs:GetQueueAttributes sqs:SetQueueAttributes |
||
| UpdateDataLakeExceptionSubscription | Grants permission to update subscriptions to the SNS topics for exception notifications | Write | |||
| UpdateSubscriber | Grants permission to update subscriber | Write |
events:CreateApiDestination events:CreateConnection events:DescribeRule events:ListApiDestinations events:ListConnections events:PutRule events:PutTargets iam:DeleteRolePolicy iam:GetRole iam:PutRolePolicy |
||
| UpdateSubscriberNotification | Grants permission to update a webhook invocation to notify a client when there is new data in the data lake | Write |
events:CreateApiDestination events:CreateConnection events:DescribeRule events:ListApiDestinations events:ListConnections events:PutRule events:PutTargets iam:CreateServiceLinkedRole iam:DeleteRolePolicy iam:GetRole iam:PassRole iam:PutRolePolicy s3:CreateBucket s3:GetBucketNotification s3:ListBucket s3:PutBucketNotification s3:PutBucketPolicy s3:PutBucketPublicAccessBlock s3:PutBucketVersioning s3:PutLifecycleConfiguration sqs:CreateQueue sqs:DeleteQueue sqs:GetQueueAttributes sqs:GetQueueUrl sqs:SetQueueAttributes |
Resource types defined by Amazon Security Lake
The following resource types are defined by this service and can be used in the
Resource
element of IAM permission policy statements. Each action in the
Actions table
identifies the resource types that can be specified with that action. A resource type can also define which condition keys you can include in a policy. These keys are displayed in the last column of the Resource types table. For details about the columns in the following table, see
Resource types table
.
| Resource types | ARN | Condition keys |
|---|---|---|
| data-lake |
arn:$
{
Partition}:securitylake:$
{
Region}:$
{
Account}:data-lake/default
|
|
| subscriber |
arn:$
{
Partition}:securitylake:$
{
Region}:$
{
Account}:subscriber/$
{
SubscriberId}
|
Condition keys for Amazon Security Lake
Amazon Security Lake defines the following condition keys that can be used in the
Condition
element of an IAM policy. You can use these keys to further refine the conditions under which the policy statement applies. For details about the columns in the following table, see
Condition keys table
.
To view the global condition keys that are available to all services, see Available global condition keys .
| Condition keys | Description | Type |
|---|---|---|
| aws:RequestTag/${TagKey} | Filters access by tags that are passed in the request | String |
| aws:ResourceTag/${TagKey} | Filters access by a tag key and value pair of a resource | String |
| aws:TagKeys | Filters access by tag keys that are passed in the request | ArrayOfString |


What kinds of variables does Ruby support? Where are they accessible? When would you use them and what makes them different?
Ruby supports four kinds of variables: Local, Instance, Class and Global Variables. Scope refers to where in a program a certain variable is accessible.
Local Variables start with a lowercase letter or an underscore and consist of letters, digits or underscores. Local variables are local to the place they are declared. For example a variable that is defined inside of a method cannot be accessed outside of that method. This variable thus has a local scope. At any given moment in a program you are in a certain local scope, and if you define a local variable in that moment it can only be accessible in the code construct that it was defined within.
Instance Variables always start with an @ sign and then consist of the same characters as the local variables. Instance variables are local to the instances of an object. If one instance of the object changes the value of the variable, when it is accessed again the variable reverts back to its original form. We can say that the change is local to the method etc. that made the change.
Class Variables consist of the same characters as instance variables but are commenced with two @@ signs. Class Variables are accessible across all instances of the class. This means that if an object changes the value of the variable, the new value will be used in all other instances of the class. A class variable is like a global variable within a class.
Global Variables are commenced with the $ dollar sign. Global variables have "Global scope" and are avaliable everywhere. Even if you start a new class or a method these global variables will remain avaliable to you. Global variables can be changed from anywhere in the program.


Hello,
I don't see a way to do an absolute value on EmonCMS?
I tried "Signed to unsigned" but it seems to give me some really funky values.
Thanks
M
Archived Forum |
|
EmonCMS - Absolute?Submitted by madas on Thu, 20/11/2014 - 16:53Hello, I don't see a way to do an absolute value on EmonCMS? I tried "Signed to unsigned" but it seems to give me some really funky values. Thanks M » |
Re: EmonCMS - Absolute?
Try:
Allow negative
× -2
+ input [the same one]
... [any other processing]
Log to Feed
Re: EmonCMS - Absolute?
I have positive and negative values - this will only fix the negative values?
Re: EmonCMS - Absolute?
Are you sure?
Re: EmonCMS - Absolute?
Do I need to log to the feed prior to the "allow negatives" in order to get the positives in the feed?
Re: EmonCMS - Absolute?
No. Why should you? What would that put into the feed?
Re: EmonCMS - Absolute?
Ah - i understand it now. Thanks for the help
Re: EmonCMS - Absolute?
In case anyone reading this thread later does not understand, this is what happens:
Say the input value is +123:
Allow negative
the value is not allowed, so zero is passed forwards.
× -2
zero × -2 = zero is passed forwards.
+ input [the same one]
0 + +123 = 123 is passed forwards.
... [any other processing]
Log to Feed
123 is sent to the feed.
Now say the input value is -321:
Allow negative
the value is allowed, so -321 is passed forwards.
× -2
-321 × -2 = +642 is passed forwards.
+ input [the same one]
+642 + -321 = 321 is passed forwards.
... [any other processing]
Log to Feed
321 is sent to the feed.
Had the input been logged to feed immediately, before 'allow negative', then two values would have been sent to the feed in succession, first the original value and then the absolute value.
Re: EmonCMS - Absolute?
This was super helpful, Robert. Thanks.
Would you happen to know of a location where all of the feed options are explained in detail? With examples, perhaps?
Re: EmonCMS - Absolute?
Unfortunately, I don't believe it exists. I have said for some while that the documentation for emonCMS needs improvement. All I can suggest is that you either take the code apart to see what it does, or test various commands and observe the result.
In general, each function accepts a value, operates on it and passes a changed value forward to the next. But there are exceptions.


Funny Money
7:30 Thur & Fri June 18, 19; 25, 26
5:00 and 8:30 Sat June 20, 27
2:00 June 21
British farce offers zany payoff
Meet Henry A Perkins, a mild mannered C.P.A. who accidently picks up the wrong
briefcase and finds it full of money. Assuming that it is illicit, Henry
decides to keep the money and move with his confused wife to Barcelona. They
wait for a cab and the doorbell rings. Henry’s attempts to extricate himself
from the charges brought against him by two detectives lead to increasing
hysterical situations.


|
Name
|
Type
|
Description
|
| balloonedMemory | xsd:long |
The size of the balloon driver in a virtual machine, in MB. The host will
inflate the balloon driver to reclaim physical memory from a virtual machine.
This is a sign that there is memory pressure on the host.
|
| compressedMemory | xsd:long |
The amount of compressed memory currently consumed by VM, in KB.
Since vSphere API 4.1
|
| consumedOverheadMemory | xsd:long |
The amount of overhead memory, in MB, currently being consumed to run a VM.
This value is limited by the overhead memory reservation for a VM, stored
in overheadMemory.
|
| distributedCpuEntitlement | xsd:long |
This is the amount of CPU resource, in MHz, that this VM is entitled to, as
calculated by DRS. Valid only for a VM managed by DRS.
|
| distributedMemoryEntitlement | xsd:long |
This is the amount of memory, in MB, that this VM is entitled to, as
calculated by DRS. Valid only for a VM managed by DRS.
|
| guestMemoryUsage | xsd:long |
Guest memory utilization statistics, in MB. This
is also known as active guest memory. The number
can be between 0 and the configured memory size of
a virtual machine.
|
| hostMemoryUsage | xsd:long |
Host memory utilization statistics, in MB. This
is also known as consummed host memory. This is between 0 and
the configured resource limit. Valid while a virtual machine is
running. This includes the overhead memory of a virtual machine.
|
| overallCpuDemand | xsd:long |
Basic CPU performance statistics, in MHz.
|
| overallCpuUsage | xsd:long |
Basic CPU performance statistics, in MHz.
|
| overheadMemory | xsd:long |
The amount of memory resource (in MB) that will be used by
a virtual machine above its guest memory requirements.
This value is set if and only if a virtual machine is registered
on a host that supports memory resource allocation features.
For powered off VMs, this is the minimum overhead required to
power on the VM on the registered host.
For powered on VMs, this is the current overhead reservation, a
value which is almost always larger than the minimum overhead, and
which grows with time. See QueryMemoryOverheadEx
|
| privateMemory | xsd:long |
The portion of memory, in MB, that is granted to a virtual machine from
non-shared host memory.
|
| sharedMemory | xsd:long |
The portion of memory, in MB, that is granted to a virtual machine from host
memory that is shared between VMs.
|
| staticCpuEntitlement | xsd:int |
The static CPU resource entitlement for a virtual machine. This value is
calculated based on this virtual machine's resource reservations, shares
and limit, and doesn't take into account current usage. This is the worst
case CPU allocation for this virtual machine, that is, the amount of CPU
resource this virtual machine would receive if all virtual machines running
in the cluster went to maximum consumption. Units are MHz.
|
| staticMemoryEntitlement | xsd:int |
The static memory resource entitlement for a virtual machine. This value is
calculated based on this virtual machine's resource reservations, shares
and limit, and doesn't take into account current usage. This is the worst
case memory allocation for this virtual machine, that is, the amount of
memory this virtual machine would receive if all virtual machines running
in the cluster went to maximum consumption. Units are MB.
|
| swappedMemory | xsd:long |
The portion of memory, in MB, that is granted to a virtual machine from the
host's swap space. This is a sign that there is memory pressure on the host.
|
|
Properties inherited from DynamicData |
| None |


Teen Spared Jail For Killing Best Friend When Prank Went Horrendously Wrong
by Lucy ConnollyA teenager who killed his best friend when he crushed his skull under his car tyre in a prank gone wrong has been spared jail.
Harrison Walker, 19, was behind the wheel of his parked car last year when his friend Garret Hurst, also 19, jumped onto his bonnet in a pub car park as a joke.
Walker drove off at around 5mph with Hurst on the bonnet of his Ford Fiesta before the latter was thrown off the vehicle when the Dukes of Hazzard-style prank went wrong.
Last month, Walker, who was 17 at the time of the incident, was found guilty of causing death by careless driving following a trial at Warwick Crown Court. Yesterday, November 12, he was handed a 12-month sentence suspended for two years and banned from driving for three years.
The court heard how Walker and his girlfriend had gone to the Crows Nest pub in Nuneaton, Warwickshire, on June 3 last year. They met friends, including Hurst and his partner, and when the group left at 9.30pm Walker agreed to drive them home.
However, when Walker got behind the wheel he pretended to drive off without Hurst – an aspiring police officer – who jumped onto the bonnet as a joke.

Hurst lost his grip and fell under the car, with the front tyre running over his head and causing multiple skull fractures along with ‘an unsurvivable brain injury’. He was rushed to hospital but, despite an emergency operation, died three days later.
Judge Andrew Lockhart QC said while Walker ‘did not deliberately run Garret Hurst over’ and while some people may think Hurst’s ‘own actions’ contributed to his death, Walker was the driver of the vehicle so ‘he alone was responsible for the quality of his driving’.
The judge said:
The prosecution say his driving fell below that to be expected, and that that contributed to Garret Hurst’s death. I believe this young man feels more sorry for himself than for anyone else.
Addressing Walker, Judge Lockhart continued:
As to your expression of remorse, I reject it. The way to show that would have been to acknowledge your guilt. This was careless driving falling not far short of dangerous driving.
Lack of driving experience had nothing to do with this. It was crass foolishness. You say you hope to join the Navy. That requires a degree of bravery, something you have conspicuously failed to show in this case. You need to learn how to take responsibility.
Walker said Hurst’s death was ‘something [he’s] got to live with now’, adding: ‘As soon as I saw him fall off, my judgment was to stop the car to see if he was OK.’
But Hurst’s heartbroken parents, Nicola and Lee, said the difficulty of having to sit through a trial and have ‘somebody read out [their] son’s injuries and the actions leading up to his death’ could not be put into words.
They described Hurst as an ambitious young man who ‘was loved by everyone he met’, and in a joint statement said: ‘I will never see Garret get married, raise a family, watch him grow into a man and see what father he would be to his children.’
Our thoughts are with Hurst’s family at this difficult time. Rest in peace, Garret.
If you have experienced a bereavement and would like to speak with someone in confidence, contact Cruse Bereavement Care via their national helpline on 0808 808 1677.
A Broadcast Journalism Masters graduate who went on to achieve an NCTJ level 3 Diploma in Journalism, Lucy has done stints at ITV, BBC Inside Out and Key 103. While working as a journalist for UNILAD, Lucy has reported on breaking news stories while also writing features about mental health, cervical screening awareness, and Little Mix (who she is unapologetically obsessed with).


The Serenity operating system turns 1 year old today. I'm counting from the first commit in the git repository, on October 10, 2018. Parts of the code had been around for a while before that, so this first commit was really about putting everything I was tinkering with into a shared repo.
Anyways... we have to start somewhere!
NOTE: This web page is very light on HTML/CSS features so that it can be rendered by Serenity's own Browser!
In the beginning there were four components:
These were just some little C++ projects I had been tinkering with after installing Slackware 11 on an old PC to do some hacking. None of them were very mature, but it was fun, and I was in a place where I needed to do some programming to find myself again.
Here's how the ext2 filesystem parser looked like when running:
::>cd /home/andreas ::>ls -l [VFS] ls ///home/andreas -> ext2fs 01:00000017 01:00000017 drwxr-xr-x 1024 2018-10-08 13:47:04 ./ 01:00000016 drwxr-xr-x 1024 2018-10-02 23:43:49 ../ 01:00000018 -rw-r--r-- 18 2018-10-02 23:44:09 file1 01:00000019 -rw-r--r-- 18 2018-10-02 23:44:14 file2 ::>
I imported a little x86 kernel I had been working on earlier in the year.  I originally had some weird idea that kernels should be written in C, so I had tried to write in C, but I thankfully realized very quickly that I was being silly. :^)
I kept working on the GUI toolkit on my Linux system, while also developing the standalone system. This is how far I got with the GUI while it was still sitting on top of SDL on Linux:
I then decided it was time to get this running on top of Serenity's own kernel. A day later, I saw this running in a VM for the first time. It was the most beautiful thing I had ever seen.
I started working on a userspace API for doing GUI stuff. The original version was a monstrosity with the window server running in the kernel and processes making syscalls to create windows, etc.
Somewhere around here I figured it would be cool to add networking support, so I started building a network stack.
And with that, this little screenshot tour of the first year of Serenity is over.
If you would like to see more, I've also been making regular monthly update videos throughout the year:
To all the boys and girls who have helped out in the last year, with code, bug reports, docs, commenting on videos, e-mailing, hanging out on IRC, retweeting, telling your friends, etc, thank you! I'm so grateful for all the love this project has been getting.
And also, a huge thank you! to everyone who has supported me via Patreon and other donation methods!  :)
Let's see what we can do in year 2!
Andreas Kling, 2019-10-10


PLAY
LEFT
RIGHT
PAUSE
MOUSE O/I
Press Mouse O/I to disable mouse. You can you keybord controls or buttons Left and Right to move


public static interface JobBuilder.ScheduleBuilder
| Modifier and Type | Method and Description |
|---|---|
ScheduledJobInfo |
add()
Finally add the job to the schedule
|
ScheduledJobInfo |
add(List<String> errors)
Finally add the job to the schedule
|
JobBuilder.ScheduleBuilder |
at(Date date)
Schedule the job for a specific date.
|
JobBuilder.ScheduleBuilder |
cron(String expression)
Schedule the job for according to the cron expression.
|
JobBuilder.ScheduleBuilder |
daily(int hour,
int minute)
Schedule the job daily at the given time.
|
JobBuilder.ScheduleBuilder |
hourly(int minute)
Schedule the job hourly at the given minute.
|
JobBuilder.ScheduleBuilder |
monthly(int day,
int hour,
int minute)
Schedule the job monthly, the time needs to be specified in addition.
|
JobBuilder.ScheduleBuilder |
suspend()
Suspend this scheduling by default.
|
JobBuilder.ScheduleBuilder |
weekly(int day,
int hour,
int minute)
Schedule the job weekly, the time needs to be specified in addition.
|
JobBuilder.ScheduleBuilder |
yearly(int month,
int day,
int hour,
int minute)
Schedule the job yearly, the time needs to be specified in addition.
|
JobBuilder.ScheduleBuilder suspend()
JobBuilder.ScheduleBuilder hourly(int minute)
minute
- Between 0 and 59.JobBuilder.ScheduleBuilder daily(int hour, int minute)
hour
- Hour of the day ranging from 0 to 23.minute
- Minute of the hour ranging from 0 to 59.JobBuilder.ScheduleBuilder weekly(int day, int hour, int minute)
day
- Day of the week, 1:Sunday, 2:Monday, ... 7:Saturday.hour
- Hour of the day ranging from 0 to 23.minute
- Minute of the hour ranging from 0 to 59.JobBuilder.ScheduleBuilder monthly(int day, int hour, int minute)
day
- Day of the month from 1 to 28.hour
- Hour of the day ranging from 0 to 23.minute
- Minute of the hour ranging from 0 to 59.JobBuilder.ScheduleBuilder yearly(int month, int day, int hour, int minute)
month
- Month of the year from 1 to 12.day
- Day of the month from 1 to 28.hour
- Hour of the day ranging from 0 to 23.minute
- Minute of the hour ranging from 0 to 59.JobBuilder.ScheduleBuilder at(Date date)
date
- The dateJobBuilder.ScheduleBuilder cron(String expression)
expression
- The cron expressionScheduledJobInfo add()
null
otherwise.ScheduledJobInfo add(List<String> errors)
errors
- Optional list which will be filled with error messages.null
otherwise.Copyright © 2015 The Apache Software Foundation. All rights reserved.


--- layout: post title: Oh Dear, not a great welcome back tags: - Business - Personal Opinion status: publish type: post published: true meta: email_notification: '1272801913' _edit_last: '451289' ---
Customer service in Australia « Alec the Geek
Australian customer service is generally pretty poor.
After writing a piece a few years showing some great examples of AU customer service I had a great example tonight of how NOT to treat customers on the Melbourne Skybus. It was the first time I had used the service and after the showing tonight I hope the last.
I had purchased my return ticket a couple of weeks ago (being concerned about the time it would take to queue up yesterday morning on my way to Sydney). The net result was that on my outward journey the ticket print had become worn (but was still legible) and this meant the driver had to punch the ticket manually and then return it. No problem so far. However tonight when I returned the driver refused to accept the ticket as it had two hole punches in it and so had supposedly been already used. My attempt to explain that this was not the case as I had only travelled up the day previously was greeted with disbelief and he started hectoring me in a loud voice. I asked him to stop shouting which only made matters worse. He eventually referred me to the ticket booth for assistance who were no help at all.
I'm guessing the first bus driver had decided that the slightly worn appearance of my ticket (it had been nestled in my wallet for two weeks) meant he was justified in clipping it for both inward and outward journeys without the courtesy of mentioning it to me!
I was forced to buy another ticket (A$16 for a 20min bus ride), was left feeling upset and embarrassed (as of course a large number of people had been able to enjoy the spectacle of me being harangued in the front of the bus).
I hope visitors to Melbourne don't often get treated to such service


This table contains entries for T cell Receptors from human and mouse in the UniProt database. Links are provided to view the original UniProt protein entries, and their display in InterPro.
|
|
SPTR
|
Protein name |
Organism |
InterPro Domain Architecture |
InterPro Graphical Match |
Function |
|
T‑cell receptor a chain |
T-cell receptor alpha chain V region HPB-MLT precursor |
Homo sapiens
|
|
MHC-antigen
binding |
||
|
|
T-cell receptor alpha chain V region CTL-L17 precursor |
Homo sapiens
|
|
MHC-antigen
binding |
||
|
|
T-cell receptor alpha chain V region PY14 precursor |
Homo sapiens
|
|
MHC-antigen
binding |
||
|
|
T-cell receptor alpha chain V region PHDS58 precursor |
Mus musculus
Mouse |
|
MHC-antigen
binding |
||
|
|
T-cell receptor alpha chain V region 2B4 precursor |
Mus musculus
Mouse |
|
MHC-antigen
binding |
||
|
T‑cell receptor b chain |
T-cell receptor beta chain V region YT35 precursor |
Homo sapiens |
|
MHC-antigen
binding |
||
|
|
T-cell receptor beta chain V region 3H.25 precursor |
Mus musculusMouse |
|
MHC-antigen
binding |
||
|
|
T-cell receptor beta chain V region 86T1 precursor |
Mus musculusMouse |
|
MHC-antigen
binding |
||
|
|
T-cell receptor beta chain V region PHDS203 precursor |
Mus musculusMouse |
|
MHC-antigen
binding |
||
|
|
T-cell receptor beta chain V region LB2 precursor |
Mus musculusMouse |
|
MHC-antigen
binding |
||
|
|
T-cell receptor beta chain V region C5 precursor |
Mus musculusMouse |
|
MHC-antigen
binding |
||
|
|
T-cell receptor beta chain V region E1 precursor |
Mus musculusMouse |
|
MHC-antigen
binding |
||
|
|
T-cell receptor beta chain V region CTL-F3 precursor |
Mus musculusMouse |
|
MHC-antigen
binding |
||
|
T‑cell receptor g chain |
T-cell receptor gamma chain V region PT-gamma-1/2 precursor |
Homo sapiens |
|
Binds free antigen |
||
|
|
T-cell receptor gamma chain V region V108A precursor |
Mus musculusMouse |
|
Binds free antigen |
||
|
|
T-cell receptor gamma chain V region V108B precursor |
Mus musculusMouse |
|
Binds free antigen |
||
|
|
T-cell receptor gamma chain V region DFL12 precursor |
Mus musculusMouse |
|
Binds free antigen |
||
|
T‑cell receptor d chain |
Hypothetical protein (predicted T cell receptor delta-chain precursor) |
Homo sapiens
|
|
Binds free antigen |
||
|
|
TRDV4 |
Mus musculus
Mouse |
|
Binds free antigen |
||
|
CD3 chains |
T-cell surface
glycoprotein CD3 delta chain precursor |
Homo sapiens
|
|
Mediates signal
transduction |
||
|
|
T-cell surface
glycoprotein CD3 epsilon chain precursor |
Homo sapiens
|
|
Mediates signal
transduction |
||
|
|
T- cell surface
glycoprotein CD3 gamma chain precursor |
Homo sapiens
|
|
Mediates signal
transduction |
||
|
|
T-cell surface
glycoprotein CD3 delta chain precursor |
Mus musculus
Mouse |
|
Mediates signal
transduction |
||
|
|
T-cell surface glycoprotein
CD3 epsilon chain precursor |
Mus musculusMouse |
|
Mediates signal
transduction |
||
|
|
T-cell surface glycoprotein
CD3 gamma chain precursor |
Mus musculusMouse |
|
Mediates signal
transduction |
||
|
|
T-cell surface glycoprotein
CD3 eta chain precursor |
Mus musculus
Mouse |
|
Probable role in assembly and expression of TCR complex, and
in signal transduction. |
||
|
z chains |
T-cell surface glycoprotein
CD3 zeta chain precursor |
Homo sapiens
|
|
Probable role in assembly and expression of TCR complex, and
in signal transduction. |
||
|
|
T-cell surface glycoprotein
CD3 zeta chain precursor |
Mus musculusMouse |
|
Probable role in assembly and expression of TCR complex, and
in signal transduction. |
||
|
CD4 receptor |
T-cell surface glycoprotein
CD4 precursor |
Homo sapiens
|
|
Accessory protein for MHC class-II antigen/T-cell receptor interaction. May regulate T-cell activation. |
||
|
|
T-cell surface
glycoprotein CD4 precursor |
Mus musculus
Mouse |
|
Accessory protein for MHC class-II antigen/T-cell receptor
interaction. May regulate T-cell activation. |
||
|
CD8 receptor |
T-cell surface
glycoprotein CD8 alpha chain precursor |
Homo sapiens |
Accessory protein for MHC class-I antigen/T-cell receptor interaction. May play a role in process of T-cell mediated killing. |
|||
|
|
T-cell surface
glycoprotein CD8 beta chain precursor |
Homo sapiens
|
|
Accessory protein for MHC class-I antigen/T-cell receptor
interaction. May play a role in process of T-cell mediated killing. |
||
|
|
T-cell surface
glycoprotein CD8 alpha chain precursor |
Mus musculus
Mouse |
|
Accessory protein for MHC class-I antigen/T-cell receptor
interaction. May play a role in process of T-cell mediated killing. |
||
|
|
T-cell surface
glycoprotein CD8 beta chain precursor |
Mus musculus
Mouse |
|
Accessory protein for MHC class-I antigen/T-cell receptor
interaction. May play a role in process of T-cell mediated killing. |
||
|
CD28 |
T-cell-specific surface glycoprotein CD28 precursor |
Homo sapiens |
|
T-cell activation, the induction of cell proliferation and cytokine production and promotion of T-cell survival. |
||
|
|
T-cell-specific surface glycoprotein CD28 precursor |
Mus musculus
Mouse |
|
T-cell activation, the induction of cell proliferation and
cytokine production and promotion of T-cell survival. |
||
|
Kinases |
Tyrosine-protein
kinase ZAP-70 |
Homo sapiens
|
|
Associates with z chain. Plays a role in lymphocyte activation. |
||
|
|
Tyrosine-protein
kinase ZAP-70 |
Mus musculus
Mouse |
|
Associates with z
chain. Plays a role in lymphocyte activation. |
||
|
|
Proto-oncogene
tyrosine-protein kinase LCK |
Homo sapiens |
Antigen-induced T-cell activation. |
|||
|
|
Proto-oncogene
tyrosine-protein kinase LCK |
Mus musculus
Mouse |
|
Antigen-induced T-cell activation. |


Trading_SellingManagerSoldOrderType Class Reference
| Inherits from | NSObject |
| Conforms to | PicoBindable |
| Declared in | Trading_SellingManagerSoldOrderType.h Trading_SellingManagerSoldOrderType.m |
Tasks
-
sellingManagerSoldTransaction
Information about one line item in the order.
property -
shippingAddress
Shipping address of a buyer.
property -
shippingDetails
The shipping-related details for an order,
property
including flat and calculated shipping costs and shipping insurance costs. -
cashOnDeliveryCost
The cost of cash-on-delivery.
property -
totalAmount
Total cost in the order.
property -
totalQuantity
Total item quantity.
property -
itemCost
A SMPro seller can record the cost of the item, as calculated by the seller, in
property
this field. -
vatRate
Rate of applicable value added tax.
property -
netInsuranceFee
Total cost of shipping insurance.
property -
vatInsuranceFee
Amount of applicable value added tax insurance fee.
property -
vatShippingFee
VAT shipping fee.
property -
netShippingFee
Total shipping fee.
property -
netTotalAmount
The seller records in this field a net total amount obtained according to the
property
seller’s method of calculation. This field is returned for VAT transactions
only. -
vatTotalAmount
VAT total amount.
property -
actualShippingCost
The shipping cost paid by the seller to ship the order line item.
property
For multiple line item orders, it is possible that one order line item will have the shipping cost and the value for the other order line item will be 0.00.
Note: This is different from the field of the same name returned by GetOrders and its related calls, which contains the shipping cost paid by the buyer.
-
adjustmentAmount
Discount, or charge, to which the buyer and seller have agreed.
property
If this value is a positive value,
the amount is the extra money that the buyer pays the seller.
If this value is a negative value,
the amount is a discount the seller gives the buyer. -
notesToBuyer
Notes from the seller to the buyer.
property -
notesFromBuyer
Notes from the buyer to the seller.
property -
notesToSeller
Notes to self from seller.
property -
orderStatus
Status of the order regarding payment, shipping, feedback, and other
property
communications. -
unpaidItemStatus
The status of an unpaid item regarding final value, state of communications
property
between buyer and seller, and the filing of an Unpaid Item. -
salePrice
Amount of the accepted offer for the listing.
property -
emailsSent
Number of emails sent regarding this order.
property -
daysSinceSale
Number of days since the sale.
property -
buyerID
The user ID of the buyer.
property -
buyerEmail
The email of the buyer.
property -
saleRecordID
The sale record ID. Applicable to Selling Manager users.
property
When an item is sold, Selling Manager generates a sale record.
A sale record contains buyer information, shipping, and other information.
A sale record is displayed in the Sold view in Selling Manager.
Each sale record has a sale record ID. In the following calls,
the value for the sale record ID is in the SellingManagerSalesRecordNumber field:
GetItemTransactions, GetSellerTransactions, GetOrders, GetOrderTransactions.
In the Selling Manager calls, the value for the sale record ID is in the
SaleRecordID field. The sale record ID can be for single or multiple line item orders. -
creationTime
The sale date.
property -
refundAmount
Amount of the refund issued to the buyer. This field is only returned for a
property
DE/AT order subject to the new eBay payment process, and if a refund was
issued to the buyer. -
refundStatus
String value indicating the result of a refund (Success, Failure, Pending)
property
to the buyer for an DE/AT order subject to the new eBay payment process. -
any
(public property)
property
Properties
actualShippingCost
The shipping cost paid by the seller to ship the order line item.
For multiple line item orders, it is possible that one order line item will have the shipping cost and the value for the other order line item will be 0.00.
Note: This is different from the field of the same name returned by GetOrders and its related calls, which contains the shipping cost paid by the buyer.
@property (nonatomic, retain) Trading_AmountType *actualShippingCost
Discussion
The shipping cost paid by the seller to ship the order line item.
For multiple line item orders, it is possible that one order line item will have the shipping cost and the value for the other order line item will be 0.00.
Note: This is different from the field of the same name returned by GetOrders and its related calls, which contains the shipping cost paid by the buyer.
type : class Trading_AmountType
Declared In
Trading_SellingManagerSoldOrderType.h
adjustmentAmount
Discount, or charge, to which the buyer and seller have agreed.
If this value is a positive value,
the amount is the extra money that the buyer pays the seller.
If this value is a negative value,
the amount is a discount the seller gives the buyer.
@property (nonatomic, retain) Trading_AmountType *adjustmentAmount
Discussion
Discount, or charge, to which the buyer and seller have agreed.
If this value is a positive value,
the amount is the extra money that the buyer pays the seller.
If this value is a negative value,
the amount is a discount the seller gives the buyer.
type : class Trading_AmountType
Declared In
Trading_SellingManagerSoldOrderType.h
any
(public property)
@property (nonatomic, retain) NSMutableArray *any
Discussion
(public property)
entry type : PicoAnyElement, wrapper for primitive anyelement
Declared In
Trading_SellingManagerSoldOrderType.h
buyerEmail
The email of the buyer.
@property (nonatomic, retain) NSString *buyerEmail
Discussion
The email of the buyer.
type : NSString, wrapper for primitive string
Declared In
Trading_SellingManagerSoldOrderType.h
buyerID
The user ID of the buyer.
@property (nonatomic, retain) NSString *buyerID
Discussion
The user ID of the buyer.
type : NSString, wrapper for primitive string
Declared In
Trading_SellingManagerSoldOrderType.h
cashOnDeliveryCost
The cost of cash-on-delivery.
@property (nonatomic, retain) Trading_AmountType *cashOnDeliveryCost
Declared In
Trading_SellingManagerSoldOrderType.h
creationTime
The sale date.
@property (nonatomic, retain) NSDate *creationTime
Discussion
The sale date.
type : NSDate, wrapper for primitive date
Declared In
Trading_SellingManagerSoldOrderType.h
daysSinceSale
Number of days since the sale.
@property (nonatomic, retain) NSNumber *daysSinceSale
Discussion
Number of days since the sale.
type : NSNumber, wrapper for primitive int
Declared In
Trading_SellingManagerSoldOrderType.h
emailsSent
Number of emails sent regarding this order.
@property (nonatomic, retain) NSNumber *emailsSent
Discussion
Number of emails sent regarding this order.
type : NSNumber, wrapper for primitive int
Declared In
Trading_SellingManagerSoldOrderType.h
itemCost
A SMPro seller can record the cost of the item, as calculated by the seller, in
this field.
@property (nonatomic, retain) Trading_AmountType *itemCost
Discussion
A SMPro seller can record the cost of the item, as calculated by the seller, in
this field.
type : class Trading_AmountType
Declared In
Trading_SellingManagerSoldOrderType.h
netInsuranceFee
Total cost of shipping insurance.
@property (nonatomic, retain) Trading_AmountType *netInsuranceFee
Declared In
Trading_SellingManagerSoldOrderType.h
netShippingFee
Total shipping fee.
@property (nonatomic, retain) Trading_AmountType *netShippingFee
Declared In
Trading_SellingManagerSoldOrderType.h
netTotalAmount
The seller records in this field a net total amount obtained according to the
seller’s method of calculation. This field is returned for VAT transactions
only.
@property (nonatomic, retain) Trading_AmountType *netTotalAmount
Discussion
The seller records in this field a net total amount obtained according to the
seller’s method of calculation. This field is returned for VAT transactions
only.
type : class Trading_AmountType
Declared In
Trading_SellingManagerSoldOrderType.h
notesFromBuyer
Notes from the buyer to the seller.
@property (nonatomic, retain) NSString *notesFromBuyer
Discussion
Notes from the buyer to the seller.
type : NSString, wrapper for primitive string
Declared In
Trading_SellingManagerSoldOrderType.h
notesToBuyer
Notes from the seller to the buyer.
@property (nonatomic, retain) NSString *notesToBuyer
Discussion
Notes from the seller to the buyer.
type : NSString, wrapper for primitive string
Declared In
Trading_SellingManagerSoldOrderType.h
notesToSeller
Notes to self from seller.
@property (nonatomic, retain) NSString *notesToSeller
Discussion
Notes to self from seller.
type : NSString, wrapper for primitive string
Declared In
Trading_SellingManagerSoldOrderType.h
orderStatus
Status of the order regarding payment, shipping, feedback, and other
communications.
@property (nonatomic, retain) Trading_SellingManagerOrderStatusType *orderStatus
Discussion
Status of the order regarding payment, shipping, feedback, and other
communications.
type : class Trading_SellingManagerOrderStatusType
Declared In
Trading_SellingManagerSoldOrderType.h
refundAmount
Amount of the refund issued to the buyer. This field is only returned for a
DE/AT order subject to the new eBay payment process, and if a refund was
issued to the buyer.
@property (nonatomic, retain) Trading_AmountType *refundAmount
Discussion
Amount of the refund issued to the buyer. This field is only returned for a
DE/AT order subject to the new eBay payment process, and if a refund was
issued to the buyer.
type : class Trading_AmountType
Declared In
Trading_SellingManagerSoldOrderType.h
refundStatus
String value indicating the result of a refund (Success, Failure, Pending)
to the buyer for an DE/AT order subject to the new eBay payment process.
@property (nonatomic, retain) NSString *refundStatus
Discussion
String value indicating the result of a refund (Success, Failure, Pending)
to the buyer for an DE/AT order subject to the new eBay payment process.
type : NSString, wrapper for primitive string
Declared In
Trading_SellingManagerSoldOrderType.h
salePrice
Amount of the accepted offer for the listing.
@property (nonatomic, retain) Trading_AmountType *salePrice
Declared In
Trading_SellingManagerSoldOrderType.h
saleRecordID
The sale record ID. Applicable to Selling Manager users.
When an item is sold, Selling Manager generates a sale record.
A sale record contains buyer information, shipping, and other information.
A sale record is displayed in the Sold view in Selling Manager.
Each sale record has a sale record ID. In the following calls,
the value for the sale record ID is in the SellingManagerSalesRecordNumber field:
GetItemTransactions, GetSellerTransactions, GetOrders, GetOrderTransactions.
In the Selling Manager calls, the value for the sale record ID is in the
SaleRecordID field. The sale record ID can be for single or multiple line item orders.
@property (nonatomic, retain) NSNumber *saleRecordID
Discussion
The sale record ID. Applicable to Selling Manager users.
When an item is sold, Selling Manager generates a sale record.
A sale record contains buyer information, shipping, and other information.
A sale record is displayed in the Sold view in Selling Manager.
Each sale record has a sale record ID. In the following calls,
the value for the sale record ID is in the SellingManagerSalesRecordNumber field:
GetItemTransactions, GetSellerTransactions, GetOrders, GetOrderTransactions.
In the Selling Manager calls, the value for the sale record ID is in the
SaleRecordID field. The sale record ID can be for single or multiple line item orders.
type : NSNumber, wrapper for primitive long
Declared In
Trading_SellingManagerSoldOrderType.h
sellingManagerSoldTransaction
Information about one line item in the order.
@property (nonatomic, retain) NSMutableArray *sellingManagerSoldTransaction
Discussion
Information about one line item in the order.
entry type : class Trading_SellingManagerSoldTransactionType
Declared In
Trading_SellingManagerSoldOrderType.h
shippingAddress
Shipping address of a buyer.
@property (nonatomic, retain) Trading_AddressType *shippingAddress
Declared In
Trading_SellingManagerSoldOrderType.h
shippingDetails
The shipping-related details for an order,
including flat and calculated shipping costs and shipping insurance costs.
@property (nonatomic, retain) Trading_ShippingDetailsType *shippingDetails
Discussion
The shipping-related details for an order,
including flat and calculated shipping costs and shipping insurance costs.
type : class Trading_ShippingDetailsType
Declared In
Trading_SellingManagerSoldOrderType.h
totalAmount
Total cost in the order.
@property (nonatomic, retain) Trading_AmountType *totalAmount
Declared In
Trading_SellingManagerSoldOrderType.h
totalQuantity
Total item quantity.
@property (nonatomic, retain) NSNumber *totalQuantity
Discussion
Total item quantity.
type : NSNumber, wrapper for primitive int
Declared In
Trading_SellingManagerSoldOrderType.h
unpaidItemStatus
The status of an unpaid item regarding final value, state of communications
between buyer and seller, and the filing of an Unpaid Item.
@property (nonatomic, retain) NSString *unpaidItemStatus
Discussion
The status of an unpaid item regarding final value, state of communications
between buyer and seller, and the filing of an Unpaid Item.
type: string constant in Trading_UnpaidItemStatusTypeCodeType.h
Declared In
Trading_SellingManagerSoldOrderType.h
vatInsuranceFee
Amount of applicable value added tax insurance fee.
@property (nonatomic, retain) Trading_AmountType *vatInsuranceFee
Declared In
Trading_SellingManagerSoldOrderType.h
vatRate
Rate of applicable value added tax.
@property (nonatomic, retain) NSMutableArray *vatRate
Declared In
Trading_SellingManagerSoldOrderType.h
vatShippingFee
VAT shipping fee.
@property (nonatomic, retain) Trading_AmountType *vatShippingFee
Declared In
Trading_SellingManagerSoldOrderType.h


Calculates the minimal sample size for the Wilcoxon-Mann-Whitney test that is needed for a given power and two sided type I error rate. The method works for metric data with and without ties, count data, ordered categorical data, and even dichotomous data. But data is needed for the reference group to generate synthetic data for the treatment group based on a relevant effect. For details, see Brunner, E., Bathke A. C. and Konietschke, F: Rank- and Pseudo-Rank Procedures in Factorial Designs - Using R and SAS, Springer Verlag, to appear.
| Version: | 0.3.4 |
| Depends: | R (≥ 3.4.0) |
| Imports: | rankFD |
| Suggests: | testthat |
| Published: | 2018-07-08 |
| Author: | Arne C. Bathke [aut], Edgar Brunner [aut], Martin Happ [aut, cre], Frank Konietschke [aut] |
| Maintainer: | Martin Happ <martin.happ at aon.at> |
| BugReports: | http://github.com/happma/WMWssp/issues |
| License: | GPL-3 |
| URL: | http://github.com/happma/WMWssp |
| NeedsCompilation: | no |
| Citation: | WMWssp citation info |
| Materials: | README |
| CRAN checks: | WMWssp results |
| Reference manual: | WMWssp.pdf |
| Package source: | WMWssp_0.3.4.tar.gz |
| Windows binaries: | r-devel: WMWssp_0.3.4.zip, r-release: WMWssp_0.3.4.zip, r-oldrel: WMWssp_0.3.4.zip |
| OS X binaries: | r-release: WMWssp_0.3.4.tgz, r-oldrel: WMWssp_0.3.4.tgz |
| Old sources: | WMWssp archive |
Please use the canonical form https://CRAN.R-project.org/package=WMWssp to link to this page.


I am currently pursing a Masters degree in Computer Science from Syracuse University. I am specializing in Machine Learning and Data Mining migrated into traditional application space.
I have worked for IBM India close to 4 years. I have been deployed on various teams while working there. I began working on apps on US Healthcare along clients like Anthem and NASCO. This is where I have gained AHM certification for domain intelligence. Gradually my primary work on NodeJS and MongoDB where I had to create an application for new ICD10 patient health data aggregation. This had PHI compliant data retrieval and maintenance along with portal for the customer to view health history. I was also made the Scrum Master for another healthcare project team where I had a great time aidting my team of 20 people.
I have a bachelor of technology degree in Computer Engineering from SVNIT or as other might know as NIT,Surat. During these formative years of my life I have made great friends who helped nurture my love for code and for Gujarati food! I was a part of the local ACM Chapter where me and my friends had organized coding competitions, bootcamps, lectures and quizes. I was also the Design Head for our college festival, AutumnFest which is one of the largest college festival west of India.
I have completed the majority of my secondary education from Kendriya Vidayala at Surat. The rest was between Ryan International School, Surat and Timpany School, Vishakhapatnam. While my primary interest was in Computer Science in secondary school indulging in C++, my hobby and skill lied in Art where I had garnered many awards to my name.


Starting with Chrome 42 you are able to send push notifications to your website users, even when they are not browsing your website.
We have integrated this new feature into the Realtime Cloud Messaging Pub/Sub service to make your life easier.
You probably noticed that Chrome asked if you allowed notifications from this website. If you accepted you are already subscribed to your own private channel to receive notifications.
Your channel is: ...
This was performed through the new subscribeWithNotifications
method in the Realtime JavaScript SDK.
Demo time! Clicking on the following button will send a new push notification to your private channel (only you'll see the push).
You should see a Chrome Push Notification pop-up like this near your system tray (the first push may take a little more time to be delivered due to the underlying Google Cloud Messaging backend configuration).
This example uses a private channel for each user so you can send pushes at will, without annoying other users. A typical use case in a website would be using a global channel and subscribing each user to that channel. This way you could broadcast a single push to all users simultaneously. It´s powerful but should be used wisely.
No problem, if an instance of Chrome is running users will see your notification pop-up inviting them back to your website. If Chrome is not running the pop-up will be shown as soon as Chrome is launched.
Let's try it. Copy the following curl command and navigate away from this website. Paste the command in your terminal window and send yourself a push notification. When you receive it click on the pop-up to comeback to this page.
The command above is simply sending a Realtime message to your private channel (the C parameter) using the Realtime REST API. The Realtime server will take care of broadcasting it to Google Cloud Messaging.
Yes it will, with no code changes.
If you have an Android device with Chrome 42+ installed just navigate to this page and copy your private channel. Then replace the channel name in the curl above (the C parameter) and give it a go.
But the good news won't stop here. Taking advantage of the Realtime Cloud Messaging integration with GCM for Android devices and APNS for iOS/OSX devices, now you'll be able to send one single push to your entire user base in almost all platforms. Until now you could only do it with native mobile apps, now you can do it also for your website users.
We are currently working hard to add support for Safari OSX website push notifications also.
You'll find this example source code and starting guide at https://github.com/realtime-framework/ChromePushNotifications
Follow the guidelines and in less than one hour you'll be engaging with your website users. Go for it ...


I like cooking
I like music
I like video games
I like movies
I like snakes
I like Italian and American food
I like sleeping
I like programming
I like technology
I like this picture below enough to put it on two websites I've made
I also like whatever this song is.


Currently we don't have any more tutorials here, but check out more material at http://academy.appgyver.com!
http://academy.appgyver.com
Try generating an AngularJS resource:
$ steroids generate ng-resource
Happy Hacking!


Comment out the line "WaitForMouseClick()" by entering a "#" at the beginning
of the line like "#WaitForMouseClick()", then run the program.
Change "image = ReadImage('1-pets.jpg')" to "image = ReadImage('mypets.jpg')".
This will cause an error unless the file "1-pets.jpg" is copied to "mypets.jpg"
Make a knock knock joke. This could take 3 images, so add extra lines
for reading another image, displaying another image, and waiting for another mouse click.
Advanced
Remove all ReadImage, DrawImage and WaitForMouseClick lines.
Then add the following lines and note that spaces are important:
for number in range(1, 2):
image = ReadImage('2-fish-' + str(number) + '.png')
DrawImage(image)
WaitForMouseClick()
Note that there is a list of spiders that is used to find out whether the
bug touched the spiders. Commenting out the line objects.append(spider) like
"#objects.append(spider)" will not beep or change the score.
Remove the #, and add the "if i < 20:" before objects.append(spider) and the bug will
only touch half of the spiders. Note that spaces are important:


Real Madrid star Eden Hazard takes subtle dig at his former managers Antonio Conte and Maurizio Sarri
by HarigovindReal Madrid star Eden Hazard seems to enjoy his life in Spain, as he recently claimed that training under his manager Zinedine Zidane feels far better than it ever did while he worked under Antonio Conte and Maurizio Sarri, his last two managers at Chelsea.
Hazard said that it was “much less fun” training with Conte and Sarri at Stamford Bridge, in a recent interview with L’Equipe.
“The training is always with the ball,” he said, before adding:
“When you have experimented with Italians, as I have done with Conte or Sarri, you have much less fun. Everything is more framed.”
Upon asked to compare Sarri’s style of management with that of Zidane’s, the 28-year-old replied: “It’s hard to compare.”
“I was attracted to Zidane at Madrid and felt very identified. He fascinates me and has even some power over me. During Euro 2016 he told me: ‘It would be good if you came’. And when Zidane calls you it’s hard to say no.”
“He loves his players and you feel that the dressing room is happy to have him as a coach.”
The former LOSC Lille star further went on to say that joining Real Madrid had been a “lifelong dream” for him.
“It was a dream to get here,” he said, before adding:
“Ever since I started playing in my garden as a kid, they were the club I supported. Zidane was my idol. When I watched him on television he was magic.”
“The stadium, when I saw it on television, was magical. And the white jersey, impeccable. For me it was exceptional,” Hazard concluded.
Quotes via Goal.


public final class ThreadCheck
extends java.lang.Object
Usage: Call prohibitLongOps()
from a UI thread (once is sufficient)
to indicate that the thread must remain responsive. In code that does
something long-running (e.g., read a file, access a network connection, or
perform a computation longer than about 100ms), call
checkLongOpsAllowed()
to catch cases where the code has been invoked
incorrectly on a time-critical thread.
| Modifier and Type | Field and Description |
|---|---|
static java.lang.String |
LONG_OPS_LOGGED_PROPERTY
the system property name that controls whether or not an log entry is
created
|
static java.lang.String |
LONG_OPS_PROPERTY
the system property name that controls whether or not an exception is
thrown or just logged
|
| Modifier and Type | Method and Description |
|---|---|
static void |
checkLongOpsAllowed()
If the invoking thread is prohibited from performing long-running
operations and disallow.server.ops.on.ui.thread system property is set to
true, throws an exception, otherwise just logs the error.
|
static boolean |
longOpsProhibited()
Returns whether it is illegal to call a long-running operation (ones
tagged &at;LongOp) from the calling thread.
|
static void |
prohibitLongOps()
Declares that it is illegal to call a long-running operation (ones tagged
&at;ServerOp) from the calling thread.
|
static void |
runProhibitingLongOps(java.lang.Runnable runnable)
Runs the given runnable prohibiting long-running operations.
|
static void |
throwExceptionOnLongOp(boolean value)
Specifies what to do if a thread calls a long running operation after
calling prohibitLongOps().
|
public static final java.lang.String LONG_OPS_PROPERTY
public static final java.lang.String LONG_OPS_LOGGED_PROPERTY
public static boolean longOpsProhibited()
false
.true
if long-running operations are prohibited,
and false
if long-running operations are allowedpublic static void checkLongOpsAllowed() throws java.lang.IllegalStateException
Call this method from inside the implementation of a long-running
operation to help callers to not call this method when in a thread that
must remain responsive. It is safe to call this method from anywhere; it
will only fail if some party has deliberately marked the thread as
needing to remain responsive, via a call to prohibitLongOps()
.
java.lang.IllegalStateException
- if the invoking thread is prohibited from performing
long-running operationslongOpsProhibited()
,
prohibitLongOps()
public static void prohibitLongOps()
This operation should be called on the thread(s) used by the UI. Doing so will ensure that any attempt to perform a long-running operation on that thread will fail immediately. This is to assist with best practices for keeping UIs responsive.
Be careful which thread you call this method on. Once invoked, the thread cannot be used to call any long-running operations, and there is no way to unset this. In general, you should only be calling this method only in the UI thread (be wary of calling this method in a unit test setting where you might have no control over what other tests are running in the same thread).
public static void runProhibitingLongOps(java.lang.Runnable runnable)
runnable
- the runnable to run while long-running operations are
prohibited; must not be null
prohibitLongOps()
public static void throwExceptionOnLongOp(boolean value)
value
- if true, then an exception is thrown for any thread that tries
to call a long running operation after calling
prohibitLongOps(). Otherwise the exception is only logged.


Outputs a Summary
protocol buffer containing a single scalar value.
tf.compat.v1.summary.scalar( name, tensor, collections=None, family=None )
The generated Summary has a Tensor.proto containing the input Tensor.
name
: A name for the generated node. Will also serve as the series name in
TensorBoard.tensor
: A real numeric Tensor containing a single value.collections
: Optional list of graph collections keys. The new summary op is
added to these collections. Defaults to [GraphKeys.SUMMARIES]
.family
: Optional; if provided, used as the prefix of the summary tag name,
which controls the tab name used for display on Tensorboard.A scalar Tensor
of type string
. Which contains a Summary
protobuf.
ValueError
: If tensor has the wrong shape or type.


{{ title }}
Dear {{ user_fullname }},
below you'll find a summary of UNPP notifications. {% for subject, body in messages %}
{{ forloop.counter }}
{{ subject }}
{% autoescape off %}{{ body }}{% endautoescape %}
{% endfor %}


Preparation time
less than 30 mins
Cooking time
30 mins to 1 hour
Serves
Serves 4
Valentine Warner cooks up a country pub classic of a juicy venison burger with posh coleslaw and chips.
For the celeriac remoulade, place the egg yolks, mustards and vinegar into the bowl of a food processor and blend until well combined.
With the motor still running, gradually add the sunflower oil in a thin stream, until the mixture thickens and becomes smooth and glossy. (If the mayonnaise starts to thicken too quickly, loosen it with the tiniest drop of warm water, then continue.)
Add the olive oil in the same way, until the mixture is creamy in texture. Taste and add a drop or two more vinegar, if necessary. Season to taste with salt.
Peel the celeriac, then slice to a 1mm thickness using a mandolin or very sharp knife. Pile the celeriac slices on top of each other, then cut the slices into thin strips using a sharp knife. Work as quickly as possible to prevent the celeriac from discolouring. Alternatively, grate the celeriac.
Mix the celeriac with the dill in a large mixing bowl, then add enough mayonnaise to bind it together. Set aside for 30 minutes.
Meanwhile, for the chips, rinse the potato fries under cold water, then drain well and pat dry using kitchen paper. Dry as thoroughly as possible.
Heat the oil in a deep-fat fryer to 140C/285F. Alternatively, heat the oil in a deep-sided, heavy-based pan until a breadcrumb sizzles and turns golden-brown when dropped into it. (CAUTION: hot oil can be dangerous. Do not leave unattended.)
When the oil is hot, add the chips (in batches if necessary) and fry for three minutes. Remove from the pan using a slotted spoon and set aside to drain in a colander lined with kitchen paper.
Increase the heat to 180C/350F, then return the chips to the hot oil and fry for five minutes, or until lightly golden-brown. Remove from the oil again and drain in the colander (lined with fresh pieces of kitchen paper). Season with salt and keep warm.
For the venison burger, season the venison mince with salt and freshly ground black pepper. Shape the seasoned mince into four thick burgers. Rub each burger all over with a little olive oil.
Heat a griddle pan over a medium to high heat. When the pan is smoking, add the burgers and cook for 3-4 minutes on each side (for medium), or until brown griddle marks have appeared on the outside of the burgers and the burgers are cooked to your liking.
To serve, place each burger into a bread roll and top with red onion, gherkins and a dollop of ketchup, if desired. Place the burgers onto four plates. Serve the chips and celeriac remoulade alongside.


Geological Models for Explorations of Dynamic Earth
The GEODE project is developing a new and improved version of Seismic Explorer software. The Seismic Explorer model allows users to see patterns of earthquakes on Earth, including magnitude, depth, location and frequency. We have added new data sets related to volcanic eruptions, and we will be adding additional data sets related to the rate and direction of plate motion and plate boundaries. Seismic Explorer automatically updates its database of earthquakes, allowing you to explore recent events in the classroom. With Seismic Explorer, you can explore patterns of earthquakes and volcanic eruptions as they relate to topographic features such as mountains, ocean trenches, and river valleys.
GEODE is also developing a new geodynamic plate tectonic model for middle school Earth science classrooms. The software will include a system of plates bounded on all sides by other plates that interact like those found on Earth, providing an environment where students can correlate surface geologic features and events to plate interactions.
Want to learn more about the project and its research? Check out the GEODE project page
We're looking for enthusiastic teachers to use our new models, try activities, and provide us with feedback. Join the team!


I am a graduate student at Technical University of Denmark, where I work on computer vision, data compression and machine learning in IoT, etc. I have recently completed my master degree in Telecommunication(GPA:10.14/12 in Denmark grading system, approximately 3.85/4.0), DTU Fotonik, where I was supervised by Prof. Søren Forchhammer.
Email  /  Google Scholar  /  GitHub
This project is my master thesis(Grade: 12/12), which proposed a learning-based method to synthesize novel views of a light field (LF) image. Specifically, we utilize four corner LF views from a 4D LF and synthesize any in-between views via sequential convolutional neural networks(CNNs), consisting of a mask selection network and an inpainting network. Experimental results show that the proposed method outperforms other three state-of-the-art approaches.
In this project, we proposed a method termed AptBLE, that switches the PHY mode in Bluetooth5 adaptively by considering the Received Signal Strength Indicator (RSSI) level. Specifically, we optimise the RSSI threshold for different PHY modes using the K-means clustering algorithm. Moreover, based on AptBLE, we further enable the Data Length Extension (DLE) feature and term the improved method as AptBLEM. We implement AptBLE (M) on the boards and test in indoor environment. The experimental results show that AptBLE is more flexible, robust and outperforms the original fixed PHY mode in terms of throughput and transmission range. Furthermore, AptBLEM can triple the throughput than AptBLE, with a maximum throughput value in 1035Kbps and 42m range in indoor environment.
I'm interested in devleoping different tasks for computer vision (e.g. view synthesis, super-resolution, object detection and style transfer) using deep learning models such as deep Convolutional Neural Networks(CNNs) and Vision Transformer(ViT).


This small component demonstrates how to automatically stop and remove all views, queries, promise chains, timers, css and dom, in a single command, using jFactory
Documentation


Optional PubTal Plugins.
Plugins can be used to add support for additional content types or upload methods. Several plugins are installed by default, and the content types that they provide are described elsewhere in this manual.
Several plugins are provided that are not installed by default, but included with PubTal in the "optional-plugins" directory. These are documented here.
The pytextile.py plugin provides support for the Textile content type. In addition to the properties listed in the Template Basics section, Textile content also generates an additional property: rawContent.
This is available on the page object (i.e. the TAL path is page/rawContent), and holds a copy of the Textile content in its unparsed form.
The abiwordContent plugin provides support for the Abiword content type. In addition to the properties listed in the Template Basics section, Abiword content also generates an additional property: footnotes.
This is available on the page object (i.e. the TAL path is page/footnotes), and holds a list of footnotes. These can be used in a template as follows:

Foonotes go here

This is a complex content type provided by CSVPlugin. The plugin registers the file extension *.csvst as containing CSVSortedTables content. The file format of the *.csvst file is similar to that of the PubTal site configuration file, i.e. directives with options. The file defines a source CSV file that contains comma separated values, with the first row in the file being the name of each column. The file then goes on to define the pages that should be produced based on the CSV file, including any sorting that should be applied to the data.
Here is an example of a *.csvst file that demonstrates all of the options available:
source-file employees-file.csv
<Page employeesByName.html>
header title Employees sorted by Name
<sort name>
</sort>
</Page>
<Page employeesByLevel.html>
header title Employees sorted by Level, then Name
<sort level>
value VP 0
value Manager 1
value Team Lead 2
empty-value 3
</sort>
<sort name>
</sort>
</Page>
The source-file option must come first, and specifies the source CSV data file (relative to the *.csvst file). The <Page pageName.html> directives can contain header options that define name-value pairs. The pageName.html is the exact name of the page to be generated.
The <sort column-name> directives must be nested within the <Page> directives, and define how the data should be sorted. The order of the <sort> directives defines which column is sorted first. Within the directive two options can be used: value and empty-value. The value option is used to map a column value to a sort priority; the lower the priority the higher up in the list it appears. The empty-value option defines the sort priority to use for an empty value. If no options are specified the column will be sorted by alphabetical order.
The CSVSortedTables content type provides the CSV data through page/content as a list. To access column values for a particular row use the name of the column. As an example the template for the employee csvst file above could be:

Employee Name
Employee Level

PubTal Version 3.5


| 0 |
https://mledits.github.io/icse_sp5/5/25169/details.html |
| 1 |
https://mledits.github.io/icse_sp5/20/3992/details.html |
| 2 |
https://mledits.github.io/icse_sp5/3/6664/details.html |
| 3 |
https://mledits.github.io/icse_sp5/6/38733/details.html |
| 4 |
https://mledits.github.io/icse_sp5/6/34281/details.html |
| 5 |
https://mledits.github.io/icse_sp5/5/32329/details.html |
| 6 |
https://mledits.github.io/icse_sp5/8/39642/details.html |
| 7 |
https://mledits.github.io/icse_sp5/3/51193/details.html |
| 8 |
https://mledits.github.io/icse_sp5/5/14140/details.html |
| 9 |
https://mledits.github.io/icse_sp5/8/39122/details.html |
| 10 |
https://mledits.github.io/icse_sp5/6/29822/details.html |
| 11 |
https://mledits.github.io/icse_sp5/5/34046/details.html |
| 12 |
https://mledits.github.io/icse_sp5/12/839/details.html |
| 13 |
https://mledits.github.io/icse_sp5/3/51194/details.html |
| 14 |
https://mledits.github.io/icse_sp5/7/8946/details.html |
| 15 |
https://mledits.github.io/icse_sp5/19/51617/details.html |
| 16 |
https://mledits.github.io/icse_sp5/6/11858/details.html |
| 17 |
https://mledits.github.io/icse_sp5/8/40777/details.html |
| 18 |
https://mledits.github.io/icse_sp5/7/43817/details.html |
| 19 |
https://mledits.github.io/icse_sp5/8/62682/details.html |
| 20 |
https://mledits.github.io/icse_sp5/7/32000/details.html |
| 21 |
https://mledits.github.io/icse_sp5/20/10038/details.html |
| 22 |
https://mledits.github.io/icse_sp5/7/55964/details.html |
| 23 |
https://mledits.github.io/icse_sp5/4/43946/details.html |
| 24 |
https://mledits.github.io/icse_sp5/17/57564/details.html |
| 25 |
https://mledits.github.io/icse_sp5/5/11432/details.html |
| 26 |
https://mledits.github.io/icse_sp5/5/13096/details.html |
| 27 |
https://mledits.github.io/icse_sp5/6/15715/details.html |
| 28 |
https://mledits.github.io/icse_sp5/6/20356/details.html |
| 29 |
https://mledits.github.io/icse_sp5/7/37118/details.html |
| 30 |
https://mledits.github.io/icse_sp5/3/61630/details.html |
| 31 |
https://mledits.github.io/icse_sp5/6/71313/details.html |
| 32 |
https://mledits.github.io/icse_sp5/6/54491/details.html |
| 33 |
https://mledits.github.io/icse_sp5/7/26893/details.html |
| 34 |
https://mledits.github.io/icse_sp5/8/58294/details.html |
| 35 |
https://mledits.github.io/icse_sp5/13/72650/details.html |
| 36 |
https://mledits.github.io/icse_sp5/5/3976/details.html |
| 37 |
https://mledits.github.io/icse_sp5/7/49345/details.html |
| 38 |
https://mledits.github.io/icse_sp5/7/57492/details.html |
| 39 |
https://mledits.github.io/icse_sp5/14/8118/details.html |
| 40 |
https://mledits.github.io/icse_sp5/3/56962/details.html |
| 41 |
https://mledits.github.io/icse_sp5/3/38896/details.html |
| 42 |
https://mledits.github.io/icse_sp5/17/15892/details.html |
| 43 |
https://mledits.github.io/icse_sp5/24/72414/details.html |
| 44 |
https://mledits.github.io/icse_sp5/7/27018/details.html |
| 45 |
https://mledits.github.io/icse_sp5/7/24857/details.html |
| 46 |
https://mledits.github.io/icse_sp5/3/18271/details.html |
| 47 |
https://mledits.github.io/icse_sp5/4/62179/details.html |
| 48 |
https://mledits.github.io/icse_sp5/6/1845/details.html |
| 49 |
https://mledits.github.io/icse_sp5/3/24296/details.html |
| 50 |
https://mledits.github.io/icse_sp5/13/14129/details.html |
| 51 |
https://mledits.github.io/icse_sp5/7/27479/details.html |
| 52 |
https://mledits.github.io/icse_sp5/4/29888/details.html |
| 53 |
https://mledits.github.io/icse_sp5/13/1875/details.html |
| 54 |
https://mledits.github.io/icse_sp5/18/45812/details.html |
| 55 |
https://mledits.github.io/icse_sp5/3/20818/details.html |
| 56 |
https://mledits.github.io/icse_sp5/13/1269/details.html |
| 57 |
https://mledits.github.io/icse_sp5/4/22175/details.html |
| 58 |
https://mledits.github.io/icse_sp5/8/3281/details.html |
| 59 |
https://mledits.github.io/icse_sp5/4/41533/details.html |
| 60 |
https://mledits.github.io/icse_sp5/13/62723/details.html |
| 61 |
https://mledits.github.io/icse_sp5/15/54929/details.html |
| 62 |
https://mledits.github.io/icse_sp5/5/14043/details.html |
| 63 |
https://mledits.github.io/icse_sp5/16/60332/details.html |
| 64 |
https://mledits.github.io/icse_sp5/7/45929/details.html |
| 65 |
https://mledits.github.io/icse_sp5/4/6509/details.html |
| 66 |
https://mledits.github.io/icse_sp5/4/14194/details.html |
| 67 |
https://mledits.github.io/icse_sp5/8/19138/details.html |
| 68 |
https://mledits.github.io/icse_sp5/6/55860/details.html |
| 69 |
https://mledits.github.io/icse_sp5/6/10077/details.html |
| 70 |
https://mledits.github.io/icse_sp5/9/8618/details.html |
| 71 |
https://mledits.github.io/icse_sp5/3/53209/details.html |
| 72 |
https://mledits.github.io/icse_sp5/6/18865/details.html |
| 73 |
https://mledits.github.io/icse_sp5/6/11691/details.html |
| 74 |
https://mledits.github.io/icse_sp5/8/66939/details.html |
| 75 |
https://mledits.github.io/icse_sp5/5/42121/details.html |
| 76 |
https://mledits.github.io/icse_sp5/17/38597/details.html |
| 77 |
https://mledits.github.io/icse_sp5/21/56863/details.html |
| 78 |
https://mledits.github.io/icse_sp5/11/48241/details.html |
| 79 |
https://mledits.github.io/icse_sp5/6/26981/details.html |
| 80 |
https://mledits.github.io/icse_sp5/4/25926/details.html |
| 81 |
https://mledits.github.io/icse_sp5/4/3397/details.html |
| 82 |
https://mledits.github.io/icse_sp5/7/16862/details.html |
| 83 |
https://mledits.github.io/icse_sp5/8/54720/details.html |
| 84 |
https://mledits.github.io/icse_sp5/5/57784/details.html |