Last updated: 2018-06-22
workflowr checks: (Click a bullet for more information) ✔ R Markdown file: up-to-date
Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.
✔ Environment: empty
Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.
✔ Seed:
set.seed(1)
The command set.seed(1)
was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.
✔ Session information: recorded
Great job! Recording the operating system, R version, and package versions is critical for reproducibility.
✔ Repository version: 5afe6c0
wflow_publish
or wflow_git_commit
). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:
Untracked files:
Untracked: output/44binary.txt.gz
Untracked: output/bmaonlybetasd5lfsr.txt.gz
Untracked: output/bmaonlybetasd5posterior.means.txt.gz
Untracked: output/independentsim.rds
Untracked: output/independentsimesd05.rds
Untracked: output/independentsiminputdata
Untracked: output/independenttest.txt
Untracked: output/indsim05sdlfsr.txt.gz
Untracked: output/indsim05sdposterior.means.txt.gz
Untracked: output/logBFTABLEapril.txt
Untracked: output/noashsharedwithzerobmaalllfsr.txt.gz
Untracked: output/noashsharedwithzerobmaallposterior.means.txt.gz
Untracked: output/sharedashcutoffomega2jun15lfsr.txt.gz
Untracked: output/sharedashcutoffomega2jun15posterior.means.txt.gz
Untracked: output/sharedtest
Untracked: output/simdata.rds
Untracked: output/univariate.ash.lfsr.txt.gz
Untracked: output/univariate.ash.pm.txt.gz
Untracked: output/univariate.ash.pmindesd.txt.gz
Untracked: output/univariate.ashind.lfsresd.txt.gz
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
| File | Version | Author | Date | Message |
|---|---|---|---|---|
| html | 3ab329f | Peter Carbonetto | 2018-06-18 | Build site. |
| Rmd | 6314ce0 | Gao Wang | 2018-06-16 | Relabel ‘test’ to ‘strong’ in data and code |
| html | 6eee6a9 | Peter Carbonetto | 2018-06-06 | Updated the webpages for a bunch of R Markdown files after minor revisions. |
| Rmd | 2b0db9b | Peter Carbonetto | 2018-06-06 | Misc. revisions to Rmd files. |
| Rmd | 5222572 | Peter Carbonetto | 2018-06-06 | Some misc. updates to the R Markdown files. |
| html | 48f7ba8 | Peter Carbonetto | 2018-06-06 | Created new webpage for HeterogeneityTables analysis. |
| Rmd | 9079466 | Peter Carbonetto | 2018-06-06 | wflow_publish(c(“gtex.Rmd”, “HeterogeneityTables.Rmd”)) |
| Rmd | 35ca901 | Peter Carbonetto | 2018-06-06 | Revised data/results loading steps in HeterogeneityTables.Rmd. |
| Rmd | 4625ae8 | Peter Carbonetto | 2018-06-06 | Renamed HeterogeneityTables analysis files. |
| html | 4625ae8 | Peter Carbonetto | 2018-06-06 | Renamed HeterogeneityTables analysis files. |
Here we summarize overall sharing of effects by sign and by magnitude. Compare the table at the bottom of this page against Table 2 in the manuscript.
Because a major feature of these data is that brain tissues generally show more similar effects than non-brain tissues, we also compute results separately from subsets of brain and non-brain tissues.
First, we load some functions defined for mash analyses.
source("../code/normfuncs.R")
This is the threshold used to determine which genes have at least one significant effect across tissues.
thresh <- 0.05
Load some GTEx summary statistics, as well as some of the results generated from the mash analysis of the GTEx data.
out <- readRDS("../data/MatrixEQTLSumStats.Portable.Z.rds")
maxbeta <- out$strong.b
maxz <- out$strong.z
standard.error <- out$strong.s
out <- readRDS(paste("../output/MatrixEQTLSumStats.Portable.Z.coved.K3.P3",
"lite.single.expanded.V1.posterior.rds",sep = "."))
pm.mash <- out$posterior.means
pm.mash.beta <- pm.mash*standard.error
lfsr <- out$lfsr
lfsr[lfsr < 0] <- 0
tissue.names <- as.character(read.table("../data/abbreviate.names.txt")[,2])
colnames(lfsr) <- tissue.names
Load the results generated from the mash analysis of the GTEx data after removing the data from the brain tissues.
lfsr.nobrain <- read.table("../output/nobrainlfsr.txt")[,-1]
colnames(lfsr.nobrain) <- tissue.names[-c(7:16)]
pm.mash.nobrain <-
as.matrix(read.table("../output/nobrainposterior.means.txt")[,-1]) *
standard.error[,-c(7:16)]
Load the results generated from the mash analysis of the GTEx data for the brain tissues only.
lfsr.brain.only <- read.table("../output/brainonlylfsr.txt")[,-1]
colnames(lfsr.brain.only) <- tissue.names[c(7:16)]
pm.mash.brain.only <-
as.matrix(read.table("../output/brainonlyposterior.means.txt")[,-1]) *
standard.error[,c(7:16)]
Compute the amount of eQTL sharing by sign, in all tissues, and separately in brain and non-brain tissues. “Sharing by” sign requires that the effect has the same sign as the strongest effect among tissues.
sigmat <- (lfsr<=thresh)
nsig <- rowSums(sigmat)
signall <- mean(het.norm(pm.mash.beta[nsig>0,])>0)
sigmat <- (lfsr[,-c(7:16)]<=thresh)
nsig <- rowSums(sigmat)
signall.nobrain <- mean(het.norm(pm.mash.beta[nsig,-c(7:16)])>0)
sigmat <- (lfsr[,c(7:16)]<=thresh)
nsig <- rowSums(sigmat)
signall.brainonly <- mean(het.norm(pm.mash.beta[nsig>0,c(7:16)])>0)
sigmat <- (lfsr.nobrain<=thresh)
nsig <- rowSums(sigmat)
signnobrain <- mean(het.norm(pm.mash.nobrain[nsig>0,])>0)
sigmat <- (lfsr.brain.only<=thresh)
nsig <- rowSums(sigmat)
signbrainonly <- mean(het.norm(pm.mash.brain.only[nsig>0,])>0)
Compute the amount of sharing by magnitude, in all tissues, and separately in brain and non-brain tissues. “Sharing by Magnitude” requires that the effect is also within a factor of 2 of the strongest effect.
sigmat <- (lfsr<=thresh)
nsig <- rowSums(sigmat)
magall <- mean(het.norm(pm.mash.beta[nsig>0,])>0.5)
sigmat <- (lfsr[,-c(7:16)]<=thresh)
nsig <- rowSums(sigmat)
magall.excludingbrain <- mean(het.norm(pm.mash.beta[nsig>0,-c(7:16)]) > 0.5)
sigmat <- (lfsr[,c(7:16)]<=thresh)
nsig <- rowSums(sigmat)
magall.brainonly <- mean(het.norm(pm.mash.beta[nsig>0,c(7:16)]) > 0.5)
sigmat <- (lfsr.nobrain<=thresh)
nsig <- rowSums(sigmat)
magnobrain <- mean(het.norm(pm.mash.nobrain[nsig>0,]) > 0.5)
sigmat <- (lfsr.brain.only<=thresh)
nsig <- rowSums(sigmat)
magbrain <- mean(het.norm(pm.mash.brain.only[nsig>0,]) > 0.5)
Summarize these calculations in a single table. The numbers in parentheses are obtained by the secondary mash analyses on the brain-only and non-brain tissue subsets.
round(matrix(rbind(c(signall,signall.nobrain,signnobrain,
signall.brainonly,signbrainonly),
c(magall,magall.excludingbrain,magnobrain,
magall.brainonly,magbrain)),
nrow = 2,ncol = 5,
dimnames = list(c("shared by sign","shared by magnitude"),
c("all tissues","non-brain","(non-brain)",
"brain","(brain)"))),
digits = 3)
# all tissues non-brain (non-brain) brain (brain)
# shared by sign 0.850 0.849 0.882 0.959 0.984
# shared by magnitude 0.359 0.398 0.445 0.764 0.859
The results confirm extensive eQTL sharing among tissues, particularly among the brain tissues; sharing in sign exceeds 85% in all cases, and is as high as 96% among the brain tissues.
Sharing in magnitude is inevitably lower, because sharing in magnitude implies sharing in sign. Overall, on average 36% of tissues show an effect within a factor of 2 of the strongest effect at each top eQTL.
However, within brain tissues this number increases to 76%. That is, not only do eQTLs tend to be shared among the brain tissues, but the effect sizes tend to be quite homogeneous.
sessionInfo()
# R version 3.4.3 (2017-11-30)
# Platform: x86_64-apple-darwin15.6.0 (64-bit)
# Running under: macOS High Sierra 10.13.5
#
# Matrix products: default
# BLAS: /Library/Frameworks/R.framework/Versions/3.4/Resources/lib/libRblas.0.dylib
# LAPACK: /Library/Frameworks/R.framework/Versions/3.4/Resources/lib/libRlapack.dylib
#
# locale:
# [1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
#
# attached base packages:
# [1] stats graphics grDevices utils datasets methods base
#
# loaded via a namespace (and not attached):
# [1] workflowr_<IP_ADDRESS>00 Rcpp_0.12.17 digest_0.6.15
# [4] rprojroot_1.3-2 R.methodsS3_1.7.1 backports_1.1.2
# [7] git2r_0.21.0 magrittr_1.5 evaluate_0.10.1
# [10] stringi_1.1.7 whisker_0.3-2 R.oo_1.21.0
# [13] R.utils_2.6.0 rmarkdown_1.9 tools_3.4.3
# [16] stringr_1.3.0 yaml_2.1.18 compiler_3.4.3
# [19] htmltools_0.3.6 knitr_1.20
This reproducible R Markdown analysis was created with workflowr <IP_ADDRESS>00


The Department of Philosophy and Social Sciences (Head of the Department - Doctor of Political Sciences, Professor N. A. Latigin) was established in 1966. In the 2016/2017 academic year, the department provides teaching of 28 disciplines, including normative humanitarian disciplines; discipline on the choice of students; discipline for postgraduate students and graduate students. To date, educational and methodological support for all disciplines has been created. Developed programs and work programs, reference notes of lectures, computer programs for student knowledge control, methodical recommendations for independent work of full-time and part-time students; published textbooks, textbooks, textbooks, workshops, etc.


|
Netsuite 2016_1
|
Data Fields | |
| const | _00 = "_00" |
| const | _01 = "_01" |
| const | _02 = "_02" |
| const | _03 = "_03" |
| const | _04 = "_04" |
| const | _05 = "_05" |
| const | _06 = "_06" |
| const | _07 = "_07" |
| const | _08 = "_08" |
| const | _09 = "_09" |
| const | _10 = "_10" |
| const | _auto = "_auto" |
Static Public Attributes | |
| static | $paramtypesmap |
|
static |
| const _00 = "_00" |
| const _01 = "_01" |
| const _02 = "_02" |
| const _03 = "_03" |
| const _04 = "_04" |
| const _05 = "_05" |
| const _06 = "_06" |
| const _07 = "_07" |
| const _08 = "_08" |
| const _09 = "_09" |
| const _10 = "_10" |
| const _auto = "_auto" |


Discovery
A couple of weeks ago I was on Stackoverflow and noticed an interesting post with one of my watched tags. The post described a problem where the user had submitted a YAML manifest to their Kubernetes server and caused very high CPU/memory usage, indicating that there could be an application Denial of service issue.
The YAML posted was a lightly modified version of the YAML bomb example on this Wikipedia page about the “Billion Laughs Attack”. This is an issue mainly associated with XML parsing where recursive entities can be defined in a document and, when expanding them, the process parsing the document consumes large amounts of CPU and memory.
A bit of checking seemed to show that this indeed was a valid issue but that the resource utilization was on the client-side in kubectl
and not server-side, so it wouldn’t seem like a major issue.
That changed after conferring with Brad Geesaman and Jordan Liggitt on the Kubernetes slack as it became obvious that the Denial of Service could occur on either the client or server, depending on how the document was passed to the server. When kubectl
was used the YAML was parsed locally before being passed to the Kubernetes API server, however by using curl
the YAML could be passed directly to the API server causing the YAML to be parsed server-side.
Doing some initial testing on a local VM it was obvious that the server could be DoS’d with a relatively small number of requests and Brad checked that this could also impact cloud hosted versions. The example given did require the attacker to be able to create configMap
objects on the server, which reduced the number of potential attackers considerably, so this would be an moderately serious issue but not too bad, as it required an authenticated user.
After that though, some more investigation did show that, under some circumstances, it was possible to pass YAML to the server as an unauthenticated user, which makes the issue more serious, especially if your Kubernetes cluster is exposed to the Internet. This is a (somewhat surprisingly) common configuration, with over 200,000 Kubernetes servers being internet facing (based on statistics from Binary Edge). It won’t always be the case that older clusters are vulnerable (as it depends on the exact configuration) but it’s more likely.
After the issue had been reported to the Kubernetes security team they quickly had a CVE assigned and arranged for patch releases to be created which are dropping today, covering versions 1.13 and up.
Mitigation
There are a couple of mitigations that can be applied to avoid this being an issue for your Kubernetes cluster. Firstly, ensure that you apply the available patches or, if you are using a managed Kubernetes distribution, ensure that your vendor has patched the issue.
Secondly, consider whether your Kubernetes server needs to be directly exposed to the Internet, or whether access to it can be restricted using firewalling or placing it behind a bastion host or VPN.
Another good mitigation is to minimize or remove anonymous access from the Kubernetes API server, although care is needed here as some monitoring tools require unauthenticated access to some endpoints. Some older versions of Kubernetes allowed quite a few unauthenticated requests, including some which can trigger this issue. Removing access from the system:unauthenticated
user or setting --anonymous-auth=false
on the API server can reduce the risk of this issue being triggered on a cluster. Again, if you’re using a managed Kubernetes distribution, you’ll need to speak to your vendor about enabling those flags.
Underlying library - A tale of differing perspectives
After looking at the Kubernetes perspective, I thought it would be interesting to dig down to where this issue originated, to see if it may have a wider impact.
The affected code comes from the go-yaml library. I reported the issue to the Go security team and they got in touch with the library author. A fix, which already existed in a later version of the library, was quickly put in place for the v2 one (which was used by Kubernetes). However at this point an interesting difference of opinion cropped up.
I suggested raising a CVE for this issue to help awareness for downstream projects. The author felt that, as the original code was compliant with the YAML specification, this was unnecessary and the Go security team felt that it wasn’t their role to assign one.
Both of these positions make sense, when considered from their respective positions. But, this causes quite a serious problem from a security community perspective.
The problem is that CVEs are used by most software security tools as flags to indicate “this library needs to be upgraded”. Without a CVE it’s very likely that automated software scanning tools (that are used in many enterprises for software vulnerability management) won’t flag this issue, and that unless teams manually review the changelogs of all their dependencies (a large task) they’ll be unaware of the potential risk.
The library in question is heavily used in the Go community, with around 36000 code references on Github alone, and presumably a lot of use elsewhere as YAML is a common format in the Cloud Native space where Go is often used.
It also raises the possibility of confusion if the Kubernetes CVE is used as an ersatz stand-in for a library one. It’s already possible to see other projects which use the library referencing the Kubernetes CVE as a driver for updating their library version, which would seem very odd if you don’t know the back-story.
This is also an example of a possible expectations gap between different groups. The enterprise IT/Security communities might be expecting the CVE databases to be the canonical source of vulnerabilities that they can use to prioritise software and library upgrades but if the software development communities don’t see the necessity of always assigning a CVE, that expectation won’t hold…


Enter the clues on the left (optional). Enter the numbers underneath the blanks on the right. Use 0 if a blank is not used in the final message.
If you know where spaces (or punctuation other than a period) occurs in the message, you can enter that information below. A period denotes a blank. For example, if you know that the message is a 3-letter word followed by a five-letter word, you would enter ... ..... below.


The first thing Jin-Woo did after he got home was to bring up his Status Window
'Stat Window . '.
What he wanted to check out was the newly updated info on his Skills . His gaze scrolled past his current level, his Class and Title, and eventually arrived at the Skill Window
[Skills].
Passive Skills.
- (Unknown) Lv . MAX.
- Tenacity Lv . 1.
- Master of Shortsword Lv . MAX.
Active Skills.
- Quicksilver Lv . MAX.
- Intimidation Lv . 2.
- Violent Slash Lv . MAX.
- Dagger Rush Lv . MAX.
- Stealth Lv . 2.
- Ruler's Reach Lv . MAX.
Almost all of his bountiful skills displayed in the Skill Window had reached their level limit and evolved into their ultimate forms, or were about to evolve into one
The level cap for a skill was 3 . And when a skill reached the level cap, the number would change to 'MAX' and stopped rising any further than that . However, if he continued to increase his proficiency with the skills, they would eventually evolve into their ultimate versions . The gap between the skill's effectiveness before and after its evolution was noticeably huge
The skill 'Dash' had evolved into 'Quicksilver'
The skill 'Vital Points Targetting' had evolved into 'Violent Slash'
And 'Dagger Throw' had morphed into 'Dagger Rush'
Even the passive skill that aided with handling daggers and shortswords, 'High-Grade Dagger Technique', had evolved into 'Master of Shortsword'
The result of that last evolution was something like this . Jin-Woo summoned 'Demon King's Shortsword' out and began manipulating it this way and that on his hand
He spun the weapon seamlessly around his index finger before letting it glide up to the palm of his hand .  Jin-Woo slowly smacked his lips afterwards
'What a pity that there is no one here to appreciate this . '.
The shortsword felt like an extension of his own limb, and that was all due to the passive skill, 'Master of Shortsword'
Jin-Woo shifted his gaze over to the Skill Window while repeatedly tossing the shortsword up and down
'So, 'Intimidation' and 'Stealth' are the only two with realistic chances of getting stronger, huh . '.
Regretfully, there didn't seem to be much room for the 'Tenacity' skill to improve beyond level 1, where it had been stuck ever since he got the skill . But, that was inevitable, really
[Skill: Tenacity Lv . 1].
Passive Skill
Mana required to activate: None
You possess untiring tenacity . When your stamina drops below 30%, this skill will automatically activate and reduce all damage received by 50%
… . Because, 'Tenacity' was a skill that only activated when his stamina dropped below 30% . Obviously, he wouldn't endanger his own life just to level up one of his skills, now would he?.
Also, Jin-Woo had experienced a fair number of close shaves after that passive skill became part of his arsenal . Even then, it hadn't changed from being level 1, so that could only mean he'd need to go through an extraordinary situation just for a chance to upgrade this skill
Besides, Jin-Woo becoming far too strong also played a factor here . Just how many enemies out there could realistically drive him to a desperate corner now?.
All things considered, he had no choice but to forget about upgrading 'Tenacity' altogether
He then decided to increase his proficiency with both 'Stealth' and 'Intimidation', the latter of which he hadn't had a lot of chances to utilise until now and was stuck at level 2 as a result
Unlike 'Intimidation', which was rather difficult to activate willy-nilly anywhere as he pleased, he could activate 'Stealth' even when he was going through his daily routines
But, right now, Jin-Woo's gaze was fixed to a spot up above those skills
'Just what could this guy be?'.
He was looking at the skill simply labelled as 'Unknown' found within the passive skill list
This skill had been with him ever since he became the 'Player' . But up until now, not even its basic information had been revealed to him
'I thought it'd eventually disclose its secrets after a while, but '.
Did this skill also require him to meet some kind of a condition to be unlocked as well? Because it was labelled 'MAX' from the very beginning, he was really looking forward to finding out just what kind of skill it was, but this .
A lot of time had passed since those days, but his curiosity only managed to grow larger and larger in the meantime
'… . '.
Jin-Woo continued to stare at the 'Unknown' skill until he almost bore a hole right through it, but in the end, he shook his head in defeat . Besides, what he really wanted to confirm couldn't be found within the regular Skill Window, anyway
No, they were right below it
Indeed, he wanted to check his Class-specific skills that had all gone up a level earlier in the day
[Class-specific Skills].
Active Skill.
- Shadow Extraction Lv . 2.
- Shadow Storage Lv . 2.
- Sovereign's Territory Lv . 2.
- Shadow Exchange Lv . 2.
'So, what changed, and by how much?'.
Jin-Woo took a closer look at the information on the skills, excluding 'Shadow Exchange', which he had already taken a gander before
[Skill: Shadow Extraction].
Class-specific skill
Required Mana to activate: None.
Creates a shadow soldier by extracting Mana from the recently deceased lifeform
The odds of extraction failure will rise higher depending on the target's original Stat values, as well as the length of time since its death
Number of shadows that can be extracted: 590/1,300.
Level 2 effect 'Boost': Increases the odds of enhancing the Stats of the extracted shadow
Perhaps as a reward for such a tough levelling up process, the number of shadows he could extract had shot up to a shocking degree
'The maximum number of shadows is now 1,300?!'.
As long as his surroundings were filled with targets for Shadow Extraction, he'd be able to increase the number of his allies by well over double the current size . Not only that, there was the special added effect to consider as well, which raised the odds of the extracted shadows starting off at higher levels
'So, that's what it was '.
The reason for the boss-level Naga 'Jima' to start from level 13 was most likely due to this 'Boost' effect . It wasn't a coincidence at all
'What would've happened if I possessed this Boost effect before I made Beru into a Shadow Soldier?'.
Without a doubt, he might have gotten his hands on an even more terrifying monster
'Heh, and the wise old 'they' say that a man's greed knows no bounds, didn't they?'.
Jin-Woo smirked softly to himself and confirmed the details of his other Class-specific skills one by one . The other two skills had also received a lot of enhancements, and a new, never-before-seen effect was added to each of them, as well
A wide grin settled on Jin-Woo's lips as he read the explanations of his upgraded skills, 'Shadow Storage' and 'Sovereign's Territory'
'This is great . '.
He closed the Skill Windows with a satisfied grin on his face
There was no doubt that his growth had slowed down recently . Even then, he still managed to keep moving forward, and when he thought about the fact that there was still more room for him to grow, his heart began pounding even harder
He wanted to climb even higher and higher
'I don't know where the summit is, but '.
Every time he managed to reach and exceed his goals, his heart was filled with this indescribable happiness, a powerful bliss
Ba-thump, ba-thump!!.
Jin-Woo returned the shortsword back to Inventory and placed his hand quietly on his chest
Ba-thump, ba-thump
His heart issued pleasant noises as it continued to beat steadily
It was then, he abruptly remembered something else that happened earlier in the day
'… She said it was a scary power, didn't she?'.
He recalled the tale he heard from Cha Hae-In a few hours ago
Min Byung-Gu left a warning for him . He said that Jin-Woo was in possession of a scary power, and he needed to be circumspect about it
'Was he talking about the System?'.
Jin-Woo also was scared of the things happening to him initially as well . He felt fearful towards the System capable of creating all these unexplainable phenomena around him
However, his fears didn't last for long
He adapted to the ways of the System in no time at all . And the System quickly became the single greatest tool he possessed
Sure, there were still far too many mysteries left unanswered, but that was about it, really
'… '.
Jin-Woo's gaze drifted towards the empty air in front of him
"Just what are you?".
Of course, he didn't get an answer in return
"I mean, isn't it okay to tell me what's going on already?".
He quietly stared into the empty air as if he was expecting an answer to arrive, but rather obviously, nothing came
'Inventory . '.
Jin-Woo opened his storage to extract the black key
[Item: Key to the Karutenon temple].
Rarity .
… . has been reached
Remaining time: 249:25:07.
Here it was, the invitation sent out by the System
A week's worth of time had flown by already, and only around 250 hours remained
'What kind of answers will I find in that place?'.
Half of him was filled with expectations . And the other half, deep curiosity . His heart rate that quietened down for a bit began beating faster again . Jin-Woo lifted his hand off his chest
His thoughts of doing everything he could during the remaining time hadn't changed at all . He picked his phone up and quickly made a call
- "What can I do for you, hyung-nim?".
Yu Jin-Ho replied in a cheerful voice over the phone . Jin-Woo wasted no time and got straight into the main topic
"Hey, Jin-Ho?".
- "Yes, hyung-nim?".
"You think we'll be able to book every single high-ranking Gate opening up in our area from tomorrow onwards?".
- "Just like back when we were booking all those rank C Gates, hyung-nim?".
"Yeah, like that . ".
Yu Jin-Ho thought for a little while, before replying back with a bright-sounding voice
- "Got it, hyung-nim!".
***.
A huge crowd had gathered in the Japanese airport where the Russian rank S Hunter, Yuri Orlov, made his landing, and there was hardly any space left to even set a foot inside
The corners of Yuri Orlov's lips arched up as he took in the sight of the massive throng of Japanese people coming to see him
On the other hand, the high-ranking members of the Japanese Hunter's Association bringing the Russian home walked around with their heads lowered as if they were criminals going on a trial
'The country lacking enough talented Hunters to stop a calamity by themselves, so they must borrow the strength of Hunters from another nation . '.
Those words were what Japan used to ridicule South Korea only a few weeks ago . Yet, the exact same situation was playing itself out within the Japanese border now
The Association President Matsumoto Shigeo, as well as the Association's representatives, recalled their own past indiscretion and couldn't even dare to lift their heads up again
'If only we didn't lose our Hunters on Jeju Island '.
Matsumoto Shigeo bit his lower lip
"It's Yuri Orlov!!".
"It's him, Yuri!".
The reporters from all corners of the world discovered Yuri Orlov's triumphant figure and began madly snapping away with their cameras
Click, click, click, click, click, click-!!.
The Russian Hunter stood before them and formed a wide grin as if to proudly advertise his gold teeth
His entry procedure was taken care of in a flash . The first request Yuri Orlov received from the Japanese government was to assuage the fears of the country's citizens . And he agreed to do the request easily enough
His nickname was the 'Saviour' . This moniker came about because he had blocked up countless Gates on the brink of entering the dungeon break stage up until now
As for Yuri Orlov himself, he definitely didn't shy away from this nickname which held the potential to earn him all the wealth and fame in the world
"Are you ready, Mister Yuri Orlov?".
"Of course . ".
That evening, he was moved to a certain TV station for a live interview . It was quite obvious that the attention of the entire nation of Japan was focused on this broadcast
Once the proceedings got underway, the interviewer asked the Russian
"How will you block the Gate, Mister Yuri?".
"In the same way that I've been doing until now, obviously . ".
Yuri Orlov's expression was overflowing with relaxed, assured confidence . He raised both of his hands in the air and drew a large circle
"I'll be creating a huge magic circle . Like so, around the Gate itself . ".
The screen changed for a brief moment to show the Gate in Shinjuku . And then, the 3D diagram of the magic circle was superimposed with the image of that massive Gate
"And then, everything will be finished after I pour my magic energy into it . Whatever is inside that Gate, they won't be able to come out ever again . ".
Unfortunately, such a simple explanation wasn't enough to calm the fears of the Japanese people . The interviewer tilted his head, looking unconvinced
"Pardon me, but . is that even possible?".
Yuri Orlov's brows twitched slightly
"What is?".
The interviewer cautiously studied the Russian's mood as he asked again
"Well, the claim of one rank S Hunter being able to block up an entire rank S Gate is Shall I say that, it's a bit hard to believe?".
Suddenly, Yuri Orlov began smirking derisively
The Russian Hunter was famed for his short fuse . So, the interviewer felt quite relieved inside when Yuri Orlov chuckled instead of flying directly into an enraged state . But at the same time, the Japanese interviewer became even more unnerved then before, wondering if he had inadvertently touched that man's reverse scale
Fortunately enough, Yuri Orlov kept his smile
"If I were to continue spending my magic energy to maintain that barrier, then sure, even I wouldn't be able to pull that off . ".
He wouldn't be able to do it?.
Gulp
The interviewer swallowed his dry saliva
With the Japanese rank S Hunters having effectively announced their intentions to give up on the raid, if Yuri Orlov himself also decided to forget about the Gate, then there were no other solutions left for the Japanese people
The Russian took his time and enjoyed the sight of the stiff face of the interviewer before continuing on with his words
"However, the thing with my ability is The barrier magic circle I use absorbs magic energy from its surroundings to maintain itself . ".
" !!!".
In an instant, the interviewer's expression changed
"If that's the case, then what did you mean when you said your own magic energy was needed ?".
"It's the same principal as switching on the ignition of a car . Once my barrier gets going, it will start absorbing the magic energy and become an even sturdier and bigger fortress wall . ".
A certain ray of light descended on the faces of the interviewer as well as the filming crew after they heard that explanation
Yuri Orlov's leisurely voice was filled to the brim with undeniable self-confidence . And as if that confidence had begun spreading around like an infection, the Japanese TV crew felt their fears slowly melt away
According to his explanation, wouldn't his barrier grow tougher and stronger when there was a great amount of magic energy present in the surroundings?.
There was no need to even mention the simple fact that the magic energy being emitted by a rank S Gate was absolutely enormous . So, what would happen when such a barrier was to wrap around a Gate of that magnitude?.
It'd get all tied up by its own power, that's what . Where would anyone find a situation that better fit the idea of one falling into the trap it made itself?.
At this rate, the hardness of that barrier would become the greatest in the recorded history of mankind
Yuri Orlov pointed to the camera . He was probably pointing at the unspecified number of viewers at home with his finger .  So, all you have to do is to remember who is saving you!".
***.
Beep
The giant TV was switched off
The President of Korean Hunter's Association, Goh Gun-Hui, put the TV remote down, but his expression wasn't very good at all . Woo Jin-Cheol standing next to him asked
"What do you think, sir?".
"I can't be sure . ".
Goh Gun-Hui leaned against the couch, his expression now full of worry . He was different from his Japanese counterpart; he definitely wasn't some low-rent villain who'd deride the misfortune of his neighbouring nation
Although, that didn't mean he was willing to help them out while taking on the harsh cost his own nation might have to bear . He deliberated for a short while, before opening his mouth again
"I don't know whether Yuri Orlov will be successful in blocking up that rank S Gate or not, but ".
The eyes of the Association President Goh Gun-Hui became a lot sharper
" But, I am well aware of what will happen if he fails in his task . ".
" . It's such a relief, sir . ".
" . ?".
Goh Gun-Hui looked up at Woo Jin-Cheol with a surprised face . Only then did the latter realise that his boss had misunderstood his words . Woo Jin-Cheol hurriedly waved around his hands
"I wasn't referring to the situation in Japan, sir . But ".
Woo Jin-Cheol stopped for a second or two before finishing up his explanation
"Unlike how it is with the Japanese, I'm relieved by the fact that we have a Hunter we can wholly place our trust in . That's what I meant, sir . ".
Nod, nod
Goh Gun-Hui nodded his head greatly . There was no need for him to specifically ask who that Hunter was, either . That Hunter's presence alone imparted such a sense of security in him
"Oh, by the way . How goes it with Seong Jin-Woo Hunter-nim nowadays?".
Woo Jin-Cheol wordlessly pushed forward a piece of printed document to his boss
On it, one could find the listed locations of all the high-ranking Gates that had appeared recently around the city of Seoul and the surrounding Gyeonggi province
"Why are you giving me this, all of a sudden ?".
"Sir, can you see how many of the locations have been circled in red?".
"Looks like it's about half of all the dungeons . ".
Woo Jin-Cheol quickly wiped the cold sweat streaking down his forehead and replied
"Ah-Jin Guild wants the raid permits of all of the highlighted Gates, sir . ".
Goh Gun-Hui's eyes nearly popped out of their sockets
"These All of them?!".
"Yes, sir . That's correct . ".
< Chapter 152 > Fin


Toggle navigation
Black Belt Directives
Mastering
Angular
JS
Directives
A set of directives, whose purpose is to showcase different Angular
JS
techniques.


--- layout: page title: WUT?! --- {% include JB/setup %} {% for post in site.posts %} {% cycle 'open row': '


Operators module (quspin.operators
)¶
Classes and functions for constructing and manipulating quantum operators, and implementing Schroedinger time evolution.
Many-body operators in QuSpin are defined by a string of letters representing the operator types, together with a list which holds the indices for the lattice sites that each operator acts on.
For example, in a spin-1/2 system we can represent any multi-spin operator as:
where \(\mu_i\) can be “I”, z”, “+”, “-“, “x” or “y”. Here, \(\sigma_{i_n}^{\mu_n}\) is the Pauli spin operator acting on lattice site \(i_n\). This representation provides a way to conveniently define any multi-body spin-1/2 operator, and generalises to bosons, fermions and higher spin in a natural way.
To construct operators for different particle spieces, check out the basis constructor classes for the supported operator strings.
classes¶
|
Constructs time-dependent (hermitian and nonhermitian) operators. |
|
Constructs parameter-dependent (hermitian and nonhermitian) operators. |
|
Constructs matrix exponentials of quantum operators. |
|
Applies a quantum operator directly onto a state, without constructing the operator matrix. |
functions¶
|
Calculates the commutator of two Hamiltonians \(H_1\) and \(H_2\). |
|
Calculates the anticommutator of two Hamiltonians \(H_1\) and \(H_2\). |
|
Checks if instance is object of hamiltonian class. |
|
Checks if instance is object of quantum_operator class. |
|
Checks if instance is object of exp_op class. |
Checks if instance is object of quantum_LinearOperator class. |
|
|
save a quantum_operator to a zip archive to be used later. |
|
Load quantum_operator object from a zip archive. |


{% extends "base.html" %} {% load bootstrap5 %} {% block content %}
Have already an account? Login here


Meals
Please Upload Your Meal picture
Image must be 800px x 500px
All images that are the wrong size
will automatically be resized and will possibly
stretch to preserve 800px x 500px size
@if(imageList.iterator.hasNext){
@for(img <- imageList){


On 9 June 2017, 11 new articles were published in 11 journals.
“9/11 Is Alive and Well” Or How Critical Terrorism Studies Has Sustained the 9/11 Narrative
How Fear of Crime Affects Punitive Attitudes
What Motivates Today’s Criminal Justice Student to Become An Engaged Learner?
For Males Only? the Search For Serious, Violent, and Chronic Female Juvenile Offenders
Making Connections Across 30 Years of Family Violence Research: An Introductory Editorial
Prison Industry and Desistance From Crime: An Australian Programme
Stereotypes Influence Beliefs About Transfer and Sentencing of Juvenile Offenders
Can We Continue to Effectively Police Digital Crime?
Thinking Forward Through the Past: Prospecting For Urban Order in (victorian) Public Parks


melonJS platformer step by step creation tutorial
The final result of a step by step tutorial, showing how to create a game with melonJS, see here for more details.
Additional Credits :
- SpicyPixel.NET for the GfxLib-Fuzed assets
- noSaopRadio for the ingame music
instructions : arrow keys to move, X to jump


GSOC week1 - Singularity - (May 24, 2021 - May 30, 2021)
Introduction of Singularity
During GSOC 2021 with Redhen, We have access to The High Performance Computing Clusters located at “CWRU” that represents Case Western Reserve University. We need to have our final result run in a Singularity container on this HPC. I used Docker before, and this time I want to make an introduction to Singularity.
Before starting reading this article, I will recommand you with two resouces.
“Singularity Github”
“Introduction from San Diego Supercomputer Center”
What is a container?
A (software) container is an abstraction for a set of technologies that aim to solve the problem of how to get software to run reliably when move from one computing environment to another.What is Singularity?
Singularity is a kind of container for HPC (High Performance Computing Clusters).What can Singularity do for you?
It’s a docker for HPC, that means it can do all the things that a container can do and you can let no trust users run untrusted containers. In the meanwhile, It supports HPC hardware and scientific applications.
Container
Like what we ship goods with a container by ship, we put a huge variaty of goods in containers and ship them between warehouses, without container, it is less secured and will be a mess during the transport. As different servers or machines have different standards and different environment, we need to use container to make our applications run across different platform.Component of Singularity
Container Image: A file (or collection of files) saved on disk that stores everything you need to run a taget application or applications: code, runtime, system tools, libraries, etc.
Container Process: A container process is simply a standard(Linux) process running on top of the underlying host’s operating system and kernel, but whose software environment is defined by the contents of the container image.
Compare to Virtual Machines
Container-based applications have direct access to the host kernel and hardware and, thus, are able to achieve similar performance to native applications. In contrast, VM-based applications only have indirect access via the guest OS and hypervisor, which creates a significant performance overhead.
Illustration of the structures of container and virtual machine.
Compare to Docker
HPC systems are shared resources and Docker is not designed for it.
Docker’s security model is designed to support trusted users running trusted containers(e.g. Users can escalate to root).
Docker is not designed to support tightly-coupled, highly distributed parallel applications(MPI).
Most Common Singularity Use Cases
Building and running applications that require newer system libraries than those are available on host system.
Running commercial applications binairies that have specific OS requirements which are not met by host system.
Converting Docker containers to Singularity containers.
The Singularity Workflow
Build your Singularity containers on a local system where you have root or sudo access; e.g., a personal computer where you have installed Singularity.
Transfer your Singularity containers to the HPC system where you wnat to run them.
Run your Singularity containers on that HPC system.
Setup A singularity on HPC
It is recommanded to install the same version of Singularity used on the HPC system where you plan to run your containers. If you run on multiple HPC systems, then install the lowest version number you expect to use. It is better to use Ubuntu or Fedora-based local system. I chose to use Ubuntu 20.04 for this part.
Besides building a container there are also two interesting registry for Singularity.
- Sylabs.io HUB (commercialised)
- Singularity HUB (oringinal)
They are like docker hub where you can build, share or download images.
Useful documents
You may have a look at the detailed instructions to use Singularity Lab: Build A Container.
There is also a very useful document on Redhen about using Sigularity.
There is also an introduction of using singularity on Case Western Reserve HPC.
To install Singularity on your computer, have a look on the official documents of Singularity container.
Build an Openpose singularity container
- Write a singularity definition file we name as openpose.def here. I followed steps introduced by Frankier and Zhiqi who are GSOC2020 students. You can have a look at their github. My definition file can be found on My github.
- If you want to build Singularity container locally, you need to follow the introduction here. I chose the Sigularity version 2.5.2 which can aussi be used on my HPC server. If you want to build a container locally, you need to have enough space on your working space, it can easily take more than 1g of memory depends on your project.
- To build a container, you need to have a root access and you can use this command to get into it.
- sudo -i
To run the build process, you need the command like this: - sudo singularity build --sandbox openpose_container openpose.def
- sudo -i
- After the building process, you will find a new folder is created named openpose_container. You can shell into the container as follows (-w means “writable):
- sudo singularity shell -w openpose_container
- To create the final portable unchangeable image (after training etc.):
- sudo singularity build openpose_container.simg openpose_container
- Finally, you can either upload the whole folder of openpose_container or openpose_container.simg on your HPC. It is recommended by using rsync command than use scp. Because you need to upload some very big files only once. If the connection is interrupted, you can continue the work by reusing the same command.
- sudo rsync --progress -a ./openpose_container/ server_domain_name:~/openpose_container/
Then you can easily run this command on HPC: - singularity shell --nv --bind ./home:/home openpose_container/
- sudo rsync --progress -a ./openpose_container/ server_domain_name:~/openpose_container/
From this step, we use a new container called ubuntu_container.
If you want to a container to have a shared folder with your host, you can use the following command.
- sudo singularity shell -w --bind ~/Desktop/container:/home ubuntu_container
In this way, you can bind the folder ~/Desktop/container on your host to /home on your container, and with flag -w all modifications will resist even you exit the container.
- sudo singularity shell -w --bind ~/Desktop/container:/home ubuntu_container
To use a user in a container, but you do not in the sudoer group on HPC to change user. You can following these steps:
- Create a home folder locally and mount the home folder on a container home directory when run it with sudo.
- Add a user with the same user name on HPC and switch to this user. Install everything like Anaconda, etc.
- Upload the container(If it is already on the HPC, you do not need to do this) and the home folder on HPC.
- Then, on HPC, you can run the container by binding the home directories like what you do locally, and you will find you are using the user in the container as the same name you have in HPC and the home directory is what you created locally.
Load some necessary modules on HPC:
- module load singularity
- module load cuda
- srun -p gpu --gpus 1 --mem 4000 --cpus-per-gpu 2 --pty bash # do -h to know more options
- pestat -p gpu -w
# this will show memory usage, has to be run on another terminal
Use GPU in singularity:
- You can firstly have a look at this document from Sylab.io
- what I do is to use singularity shell --nv --bind ./home:/home --bind /usr/local/cuda-11.2:/usr/local/cuda ubuntu_container
In this way you mount cuda directory and also a list of files in /usr/bin of the host to your conatainer:
nvidia-cua-mps-control dnvidia-cuda-mps-server nvidia-debugdump nvidia-persistenced nvidia-smi - You need to add cuda path in your .bashrc and source it
export PATH=$PATH:/usr/local/cuda/bin export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib64
All articles in this blog adopt the CC BY-SA 4.0 Agreement ，Please indicate the source for reprinting！


Where You At
Profile
Chat
Feed
Information
Explore
Sign out
{% block content %}{% endblock %}
{% block miniprofile %}{% endblock %}
Total number of users: {{ user_count }}
{% for user in users %}
@{{ user.username }}
{% endfor %}
Where You At ©


What happens to me when I smoke DMT is, there's a kind of going toward it. There's a sequella of events which lead to the antechamber of the mystery.  Your whole body feels odd. You take a second toke, all the oxygen seems to have been pumped out of the room. Everything jumps into clarity. It's that visual acuity thing. You take a third toke if you're able, and then you lay back, and you see this thing which looks like a rose or a chyrsanthemum, this orange spinning flowerlike thing. It takes about fifteen seconds to form, and it's like a membrane. And then, you break through it. You break through it, and then you're in this place, and there's an enormous cheer which goes up as you pass through this membrane. Some of you may know the Pink Floyd song about how the gnomes have learned a new way to say hoo-ray? They're waiting. And you burst into this place, ... and you say, 'Am I all right? Am I all right?' That's the first question, and so then you run your mind around the track, and you say, 'Hmm. Heartbeat normal? Yeah, normal, heartbeat normal. Pulse normal? Breathing? Breathe breathe breathe, yes.' But what's right here, right here and from here out is this thing which, no matter how much science fiction you've done, no matter how much William Burroughs you've read, no matter how much time you've spent in the company of the weird, the bizarre, the autre, and the peculiar, you weren't ready: and it's completely real. It's in a way more real than the contents of ordinary reality, because, see how the shadows here are muted and there's a lot of transitional zones from one color to another and so forth? This isn't like that. This is crystalline, clear, solid, you can see the light reflected in the depths of these objects, and everything is very brightly colored, and everything is moving very, very rapidly.And there are entities there. It's not about calling them up or the whisperings of them. No, they're in your face. And they're right here, and they're worse than in your face, because what they do is, they jump into your chest and then they jump out. And you have to keep saying, 'Keep breathing, keep breathing, don't freak out, pay attention.' And the entities speak to you, and they speak both in English and another way which we'll get to in a minute. But in English what they say is, 'Do not give way to wonder. Hang on. Don't just go gaga with disbelief. Pay attention. Pay attention.' And what they're trying to do is they're trying to show you something. They are very aware of the fleeting nature of this encounter. And they say, you know, 'Don't spiral off into amazement, and start raving about God and all that. Forget that. Pay attention to what we're doing.'
And then, what they're doing is they're dancing around, they're jumping around, they're emerging explicitly out of the background, bounding toward you, jumping into your chest, bounding away, and they offer, they make offerings. And they love you, that's the other thing. They say this. They say, 'We love you. You come so rarely.  Welcome, welcome.' And they make these offerings. And the offerings are objects of some sort. And now remember, you are not changed. You're exactly the person you were a few minutes before. So you're not exalted or depressed. You're just trying to make sense of this. And the objects which they offer are like, Faberge eggs, or exquisitely tooled and enamelled pieces of machinery, but they don't have rigid outlines. The objects are themselves somehow alive, and transforming and changing.  A single one of these objects is somehow, you can tell by looking at it, this would confound my world beyond hope of recovery. It cannot exist. What I'm being shown is a tiny area where miracles are transformed.
And the creatures, the tykes, are singing. They are speaking in a kind of translinguistic glossilalia. They are actually making these objects with their voices. They are singing these things into existence. And what the message is, is 'Do what we're doing. You can do what we're doing. DO IT.' And they get quite pushy about this. They say, you know, 'Damn it, DO IT!' And you're saying, 'Bu...bu...bu...bu...' And they say, 'No, DO IT! Do it NOW! DO IT!' And you say, 'I can't handle this,' you know, and then this kind of reaction goes on for awhile. Well, then, I actually, I don't take credit for it, it was not willed, but like something comes up from inside of you. Something comes out of you, and you discover you can do it, that you can use language to condense objects into existence in this space. It's the dream of all magic, but here it is folks, happening in real time. And then they're just delighted. They just go mad with delight and turn somersaults and turn themselves inside out and they all jump into your chest at once.
And after many encounters of this sort, I mean, when I first did DMT, I couldn't bring anything out of it.  But by going back repeatedly and working at it, I think I've gotten a pretty coherent -- well, let's not go that far, I think I've got a pretty clear metaphor anyway for what's happening in there, and I think a lot of people have this experience.
When you talk to shamans, they say, 'Oh, well, yes, the helping spirits. Those are the helping spirits. They can help you cure, find lost objects, you didn't know about the helping spirits?' And you say, 'Well, I knew, but I, I had no idea that it was so literal.' And they say, 'Oh, no, that's the helping spirits.'
But then, the other thing they say, if you press a shaman, if you say, "Well, what exactly is a helping spirit?" They say, "Well, a helping spirit is an ancestor."  They say, "Well, yes, ancestor, dead person. You didn't know about ancestors apparently. This is what happens to people who die." And you say, "My God, is it possible that what we're breaking into here is an ecology of souls?" That these are not extraterrestrials from Zenebelganooby or Zeta Reticula Beta. These are the dear departed. And they exist in a realm which, for want of a better word, let's call eternity. And somehow this drug, or whatever it is, is allowing me to see across the veil. This is the lifting -- you want to talk about boundary dissolution. It's one thing to get tight to your partner, it's quite another to get tight to the dear departed of centuries past. That's a serious boundary dissolution when that happens.
What these creatures want, according to them, is they want us to transform our language somehow, and I don't know what this means. I mean, at this point in the weekend and in my life, we all are on the cutting edge, and nobody is ahead of anybody else. Clearly we need to transform our language, because our culture is created by our language, and our culture is toxic, murderous, and on a downhill bummer. Somehow we need to transform our language, but is this what they mean? That we're supposed to condense machines out of the air in front of us? How does this relate to the persistent idea, promulgated by Robert Graves and other people, that there is a primal language of poetry? That poetry as we know it is a pale, pale thing, and that at some time in the human past, people were in command of languages which literally compel belief. They compel belief, because they don't make an appeal through argument or metaphor. They compel belief because they are able to present themselves as imagery. You know, William Blake said, 'If the truth can be told so as to be understood, it will be believed.'
And it's very confusing, because you wonder, have people been doing this for thousands of years? And if so, have they always encountered this tremendous urgency on the other side? If people have been doing it for thousands of years, why is there this urgency on the part of these entities? And who exactly and what exactly are they? It appalls me, you can probably tell, that I have to talk about this, because I am not, this is not my baliwick. I mean, I'm a rationalist who's just had a very weird set of experiences, but I am a rationalist. I mean, I have no patience with channelling, you know, the lords of the many rays, the divas and, you know, there's this whole thing going around about disincarnate intellignece, mostly under the control of fairly, shall we say, non-rigorous thinkers.
The difference between my rap and, you know, the finned horned folks or somebody like that is that we have an operational method for testing my assertion. We can all smoke DMT, or you can make it your business to now find out about this, and see for yourself. And not everybody agrees with me.  But some people agree, and I think if you get two out of ten agreeing with a rap like this, then you'd better pay attention.


Written? Kitten!
Warning!
 You'll need to regularly copy and paste your text into a word processor or other application to save it permanently.
If you want your work saved even if you close your browser, upgrade to a recent version of Chrome, Firefox, Safari or Opera.
Hey!
Looks like your browser supports local storage. That's great! Your writing will be saved even if you close this page.
We can't take responsibility for things going wrong, though, so you might want to copy and paste your work to an external document every so often, just in case.


Log in
Invalid username and password.
You have been logged out.
Username
Password
Remember me
Log in


--- layout: page title: Blog date: 2015-06-27 20:12:34.000000000 +05:30 categories: [] tags: [] status: publish type: page published: true meta: _edit_last: '1' imax_hidetitle: '0' imax_show_slider: '0' imax_hide_breadcrumb: '0' author: login: admin@reportlingo email<EMAIL_ADDRESS>display_name: admin@reportlingo first_name: Ankur last_name: Gupta excerpt: !ruby/object:Hpricot::Doc options: {} ---
This is an example page. It's different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:
Hi there! I'm a bike messenger by day, aspiring actor by night, and this is my blog. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin' caught in the rain.)
...or something like this:
The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.
As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!


With the modified CBMC, API stubbing/porting and understanding of build system, we were able process libraries of Ericsson. During the test run we observed a lot of false positives on assertions since these assertions were written to handle run time errors. This we mainly attribute to the fact that existing code is not written to provide information to static analysers. As we understood in chapter chap:background and chap:implementation, static analysers work by looking at information available in the existing logic without knowing run time information. To make the best of any static analyser one has to provide run time information statically. This information can be provided as part of header in each module or function, commented information for analysers or through contracts. The code we were working had contracts and next section provides more details on contract based verification.
The source code we used for the case study was LTE baseband controller software. The code was tested and deployed into products. The model checking process on 6 major modules took little over a month. Most of the time and effort was put to avoid false positives and state space explosion. The state space explosion is still a major issue in model checking. With millions of lines of code we quite often had to choose small bounding values.
ash 2012-09-13


org-ruby version 0.6.2
by Brian Dewey http://github.com/bdewey/org-ruby
This gem contains Ruby routines for parsing org-mode files.The most significant thing this library does today is convert org-mode files to HTML or textile. Currently, you cannot do much to customize the conversion. The supplied textile conversion is optimized for extracting “content” from the orgfile as opposed to “metadata.”
Added encoding directive to support Ruby 1.9.2
Headlines with the COMMENT keyword, and the PROPERTIES drawer are not exported
Angle links in org-mode are embedded in anchor tags on html output
#+BEGIN/END_SRC lang code blocks are embedded in code tags with class that specifies the coding language
Fixed bug in code blocks when a colon was at the beginning
More than five dashes create an horizontal rule in html output (thanks Neil-Smithline!)


Which of these is a legal Java variable name? 3Sally isDivisibleBy2 sally smith sally'sC All of these are legal variable names Variable names in Java cannot begin with a digit, cannot contain spaces, and cannot contain apostrophes. Legal variable names start with a letter, and may contain letters, digits and/or underscores (the _ character) after the first letter.
3Sally isDivisibleBy2 sally smith sally'sC All of these are legal variable names
3Sally
isDivisibleBy2
sally smith
sally'sC


Several feature previews, such as icons in the case list, are also now accessible in this tab. {% endblocktrans %}


BLOOD-X is a only platform for everyone let it be common people who need blood, people who wish to do some good work by donating their blood, people who wish to save their closed ones by finding a donor as fast as possible, let it be the organizations swho wish to organize blood camp or let it be the sponserers who wish to promote their product. Here, everything works in the simplest way. To learn more click below!!
LEARN MORE !Someone has to take a good step - why don't you take it.. Donate blood now!
We dont leave anything Unnoticed.
Meet the minds behind BLOOD-X
CEO
LEAD OF DESIGN
Best blog describing about our events get featured.
Great for giving a try and sponsoring for a cause
$500
Intermediate package sponsoring for good cause
$2000
You are really expert in choosing the correct package!!
$4000
We are here to help. Want to learn more about our services? Please get in touch, we'd love to hear from you!


Import all translation units from an Excel file. This is intended to be used with Export.
The import expects the columns to be in order of
Id, Description, Meaning, Source, Target
. The first row is skipped, since it is
assumed to be a header row.
.xlsx files can be dragged and dropped onto this area.
{{ unit.source }}
{{ unit.source }}


--- layout: about1 title: About header-img: "img/about.jpg" ---
Nature enthusiast, web dev in the making!


{% extends "frame.html" %} {% block content %}
“This isn't the page you're looking for. You can go about your business.”


Former EastEnders actor Cliff Parisi joining I'm A Celebrity... Get Me Out Of Here as 12th contestant?
Cliff is well known for playing Minty in EastEnders
by Charlotte RodriguesFormer EastEnders actor Cliff Parisi is reportedly joining I'm A Celebrity... Get Me Out Of Here as the 12th contestant.
The actor, who plays Fred Buckle in Call The Midwife, is said to be joining the show later this week.
According to The Sun, a show source said: "Bosses decided that this year's latecomers will be a soap duo.
"Cliff was really popular in EastEnders and he's a big character off-screen too, so they think he'll go down really well with viewers."
Cliff joined EastEnders in 2002 as Minty Peterson.
His character worked as a mechanic for Phil Mitchell for years before his departure in 2010.
Currently Cliff is playing handyman Fred in Call The Midwife.
Cliff isn't the only one reported to be going into the jungle as Coronation Street's Andy Whyment has been heavily rumoured to be joining the show.
Read More: Beverley Callard has quit Coronation Street as Liz McDonald
Last week, Corrie fans were gutted to see that the Kirk Sutherland actor wasn't in the show's starting line-up.
The first episode of I'm A Celebrity 2019 kicked off last night (November 17 2019) and viewers saw 10 celebrities make their way into the jungle.
Read More: I'm A Celebrity: Extra Camp fans beg Joe Swash to return
Celebrities include former EastEnders actress Jacqueline Jossa, former Olympian and American reality star Caitlyn Jenner, Girls Aloud singer Nadine Coyle, Rak-Su singer Myles Stephenson, and ex-footballer and broadcaster Ian Wright.
Also in the starting line-up is Radio 1 DJ Adele Roberts, Capital Radio DJ Roman Kemp, TV presenter Kate Garraway, comedian Andrew Maxwell and former England Rugby player James Haskell.
Would you like to see Cliff on I'm A Celeb? Leave us a comment on our Facebook page @EntertainmentDailyFix and let us know.


MV(1) User Commands MV(1) NAME mv - move (rename) files SYNOPSIS mv [OPTION]... [-T] SOURCE DEST mv [OPTION]... SOURCE... DIRECTORY mv [OPTION]... -t DIRECTORY SOURCE... DESCRIPTION Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY. Mandatory arguments to long options are mandatory for short options too. --backup[=CONTROL] make a backup of each existing destination file -b like --backup but does not accept an argument -f, --force do not prompt before overwriting -i, --interactive prompt before overwrite -n, --no-clobber do not overwrite an existing file If you specify more than one of -i, -f, -n, only the final one takes effect. --strip-trailing-slashes remove any trailing slashes from each SOURCE argument -S, --suffix=SUFFIX override the usual backup suffix -t, --target-directory=DIRECTORY move all SOURCE arguments into DIRECTORY -T, --no-target-directory treat DEST as a normal file -u, --update move only when the SOURCE file is newer than the destination file or when the destination file is missing -v, --verbose explain what is being done --help display this help and exit --version output version information and exit The backup suffix is `~', unless set with --suffix or SIMPLE_BACKUP_SUF‐ FIX. The version control method may be selected via the --backup option or through the VERSION_CONTROL environment variable. Here are the val‐ ues: none, off never make backups (even if --backup is given) numbered, t make numbered backups existing, nil numbered if numbered backups exist, simple otherwise simple, never always make simple backups AUTHOR Written by Mike Parker, David MacKenzie, and Jim Meyering. REPORTING BUGS Report mv bugs to<EMAIL_ADDRESS>GNU coreutils home page: <http://www.gnu.org/software/coreutils/> General help using GNU software: <http://www.gnu.org/gethelp/> Report mv translation bugs to <http://translationproject.org/team/> COPYRIGHT Copyright © 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO rename(2) The full documentation for mv is maintained as a Texinfo manual. If the info and mv programs are properly installed at your site, the command info coreutils 'mv invocation' should give you access to the complete manual. GNU coreutils 8.12.197-032bb September 2011 MV(1)


| ChromeCacheView v1.21
Copyright (c) 2008 - 2009 Nir Sofer Web site: http://www.nirsoft.net |
| /stext <Filename> | Save the list of all cache files into a regular text file. |
| /stab <Filename> | Save the list of all cache files into a tab-delimited text file. |
| /scomma <Filename> | Save the list of all cache files into a comma-delimited text file. |
| /stabular <Filename> | Save the list of all cache files into a tabular text file. |
| /shtml <Filename> | Save the list of all cache files into HTML file (Horizontal). |
| /sverhtml <Filename> | Save the list of all cache files into HTML file (Vertical). |
| /sxml <Filename> | Save the list of all cache files to XML file. |
| -folder <Cache Folder> | Start ChromeCacheView with the specified cache folder. |
Examples:
ChromeCacheView.exe -folder "F:\Documents and Settings\Administrator\Local Settings\Application Data\Google\Chrome\User Data\Default\Cache"
ChromeCacheView.exe -folder "F:\Documents and Settings\User1\Local Settings\Application Data\Google\Chrome\User Data\Default\Cache" /shtml c:\temp\chrm.html
ChromeCacheView.exe /stext c:\temp\chrm.txt


Please specify the sprint IDs for the sprints to analyse separated by ','.e.g.: 967,123,567
Please specify the short names of the projects that are relevant for this sprint separated by ','.e.g.: TST,PROJ


Press n or j to go to the next uncovered block, b, p or k for the previous block.
| File | Statements | Branches | Functions | Lines | |||||
|---|---|---|---|---|---|---|---|---|---|
| src |
|
94.44% | 34/36 | 50% | 1/2 | 66.67% | 2/3 | 94.44% | 34/36 |
| src/Validation |
|
77.42% | 24/31 | 57.69% | 15/26 | 100% | 2/2 | 77.42% | 24/31 |
| src/config |
|
100% | 1/1 | 100% | 0/0 | 100% | 0/0 | 100% | 1/1 |
| src/controllers |
|
83.55% | 127/152 | 61.11% | 11/18 | 95.12% | 39/41 | 83.89% | 125/149 |
| src/helpers |
|
70% | 14/20 | 0% | 0/5 | 50% | 3/6 | 70% | 14/20 |
| src/middlewares |
|
64.71% | 11/17 | 50% | 2/4 | 100% | 2/2 | 64.71% | 11/17 |
| src/models |
|
100% | 9/9 | 100% | 0/0 | 100% | 0/0 | 100% | 9/9 |
| src/routers |
|
100% | 30/30 | 100% | 0/0 | 100% | 0/0 | 100% | 30/30 |
| src/services |
|
55.14% | 59/107 | 30.39% | 31/102 | 75% | 21/28 | 56.19% | 59/105 |
| src/util |
|
72.41% | 21/29 | 50% | 8/16 | 100% | 1/1 | 72.41% | 21/29 |
| test |
|
100% | 19/19 | 100% | 0/0 | 100% | 6/6 | 100% | 16/16 |


Explanation of the Asset Configuration Parameters
The asset configuration parameters affect [test connectivity] and all the other actions of the application. Below are the explanation and usage of all these parameters.
-
Base URL: The URL used to connect with the RiskSense server. It represents the RiskSense platform's API base URL where /api/v1 represents the API version. Example: https://platform.risksense.com/api/v1
-
Client Name: Name of the client. All the actions will be executed for this client.
-
API Token: It is the API token of the user.
-
Verify Server Certificate: Validate server certificate
-
Number of Retries: The value of this parameter defines the number of attempts for which the action will keep on retrying if the RiskSense API continuously returns the “500 Internal Server Error” or "429 Too Many Requests". If the intermittent error gets eliminated before the number of retries gets exhausted, then, the action execution will continue along its workflow and if the intermittent error is still persistent and all the number of retries is exhausted, then, the action will fail with the latest error message being displayed. The parameter expects a positive integer value as input. If the parameter is not provided, then 2 (default value) will be considered as the value for the parameter.
-
Backoff Factor: A backoff factor to apply between attempts after the second try (most errors are resolved immediately by a second try without a delay). The parameter expects a valid float value as input. If the parameter is not provided, then 0.3 (default value) will be considered as the value for the parameter.
- Sleep time calculation: {backoff factor} * (2 ** ({number of total retries} - 1)) seconds.
Steps to generate the API token
- Go to the RiskSense platform and open 'User Settings'.
- Navigate to the 'API TOKENS' section and click on the 'Generate' button.
- Enter the name of the new token.
Explanation of the RiskSense Actions' Parameters
Test Connectivity (Action Workflow Details)
- This action will test the connectivity of the Phantom server to the RiskSense instance by making an initial API call to the Client API using the provided asset configuration parameters.
- The action validates the provided asset configuration parameters. Based on the API call response, the appropriate success and failure message will be displayed when the action gets executed.
List Users
- Action Parameter: Max Results
- This parameter allows the user to limit the number of results. If the parameter is not provided, it will fetch by default 1000 results. The internal pagination logic is applied for fetching a large number of results.
- Example:
List Tags
- Action Parameter: Max Results
- This parameter allows the user to limit the number of results. If the parameter is not provided, it will fetch by default 1000 results. The internal pagination logic is applied for fetching a large number of results.
- Example:
List Hosts
- Action Parameter: Field Name
- This parameter allows the user to filter the result data set based on the host attributes provided as input. It allows the comma-separated values of the host attributes. The user can get the list of valid host attributes by executing the List Filter Attributes action. The uid of the filter attribute must be provided here.
Here are a few examples of host attributes: hostName, ipAddress, criticality, rs3, assessment_labels.
- Action Parameter: Operator
- This parameter allows the user to provide the operator which will be applied to the value(s) provided in the Fieldname parameter. It allows the comma-separated values of valid operators. The user can get the list of valid operators by executing the List Filter Attributes action.
Here are a few examples of the operators:
- EXACT - Filter records exactly matching the criteria.
- IN - Filter records matching any of the comma-separated values.
- LIKE - Filter the records with fieldname’s value having the string provided by the user.
- RANGE - Filter the records with fieldname’s value falling in the numerical/date range provided.
- Action Parameter: Value
- This parameter allows the user to provide the value of the host attributes, which is mentioned in the Fieldname parameter, to be considered for filter criteria. It expects a JSON formatted list of values.
- Action Parameter: Exclusivity
- This parameter allows the user to determine whether to fetch the results that are matching the filter criteria (defined by the Fieldname, Operator, and Value parameter) or to fetch the results that are not matching the filter criteria. It allows the comma-separated boolean values (true/false).
- Action Parameter: Sort By
- This parameter allows the user to provide the fieldname by which to sort the records. It allows the comma-separated values of valid host attributes. If multiple host attributes are provided, then multiple sorting will be applied starting from the left-most host attribute.
- Note - If an incorrect attribute value is provided in this parameter, then the sorting of the results by that attribute will be ignored.
- Action Parameter: Sort Direction
- This parameter allows the user to provide sorting order to be applied to the host attribute provided in the Sort By parameter. It allows the comma-separated values of valid Sort Direction(s) (ASC/DESC).
- Action Parameter: Page
- This parameter allows the user to provide the index of the page from where the results are to be fetched. It expects a numeric value as an input. If not provided, then 0 will be considered as the starting index of the page.
- Action Parameter: Max Results
- This parameter allows the user to limit the number of results. If the parameter is not provided, it will fetch by default 1000 results. The internal pagination logic is applied for fetching a large number of results.
- Note:
- The Fieldname, Operator, Value, and Exclusivity parameters are used to create a filter. So, the length of these four parameters must be the same.
- Similarly, a sorting direction is required for a host attribute that is used for sorting. So, the length of Sort By and Sort Direction parameters must be the same.
- Examples:
- List the hosts having hostname like a “test”, sorted based on the ID in descending order.
- Fieldname = hostName
- Operator = LIKE
- Value = [“test”]
- Exclusivity = false
- Sort By = id
- Sort Direction = DESC
- List the hosts that are not discovered on 2014-05-01. Results are sorted first by rs3 in ascending order and then by ID in ascending order.
- Fieldname = discoveredOn
- Operator = EXACT
- Value = [“2014-05-01”]
- Exclusivity = true
- Sort By = rs3, id
- Sort Direction = ASC, ASC
- Note: The date format is in YYYY-MM-DD. Also while using the EXACT operator, note that the expected results will be fetched only if the value provided in the Value parameter will be exactly matched. So, make sure that there are no unnecessary spaces in the Value parameter.
- List the hosts having ID 1 or 2 or 3.
- Fieldname = id
- Operator = IN
- Value = [“1,2,3”]
- Exclusivity = false
- Note: While using IN operator, note that the expected results will be fetched only if the value provided in the Value parameter will be exactly matched. So, make sure that there is no space provided between the comma and the value. Example: Incorrect Value = [“1,<space>2,3<space>”], Correct Value = [“1,2,3”]
- List the hosts having criticality in the range of 2 to 5. The maximum results to be fetched are 200.
- Fieldname = criticality
- Operator = RANGE
- Value = [“2,5”]
- Exclusivity = false
- Max Results = 200
- List the hosts having hostname like a test and rs3 value 850.
- Fieldname = hostName,rs3
- Operator = LIKE, EXACT
- Value = [“test”, “850”]
- Exclusivity = false, false
List Apps
- Action Parameter: Field Name
- This parameter allows the user to filter the result data set based on the application attributes provided as input. It allows the comma-separated values of application attributes. The user can get the list of valid application attributes by executing the List Filter Attributes action. The uid of the filter attribute must be provided here.
Here are a few examples of application attributes: name, description, criticality, assessment_labels, discovered_on.
- Action Parameter: Operator
- This parameter allows the user to provide the operator which will be applied to the value(s) provided in the Fieldname parameter. It allows the comma-separated values of valid operators. The user can get the list of valid operators by executing the List Filter Attributes action.
Here are a few examples of the operators:
- EXACT - Filter records exactly matching the criteria.
- IN - Filter records matching any one of the comma-separated values.
- LIKE - Filter the records with fieldname’s value having the string provided by the user.
- RANGE - Filter the records with fieldname’s value falling in the numerical/date range provided.
- Action Parameter: Value
- This parameter allows the user to provide the value of the application attributes, which are mentioned in the Fieldname parameter, to be considered for filter criteria. It expects a JSON formatted list of values.
- Action Parameter: Exclusivity
- This parameter allows the user to determine whether to fetch the results that are matching the filter criteria (defined by the Fieldname, Operator, and Value parameter) or to fetch the results that are not matching the filter criteria. It allows the comma-separated boolean values (true/false).
- Action Parameter: Sort By
- This parameter allows the user to provide the fieldname by which to sort the records. It allows the comma-separated values of valid application attributes. If multiple application attributes are provided, then multiple sorting will be applied starting from the left-most application attribute.
- Note - If an incorrect attribute value is provided in this parameter, then the sorting of the results by that attribute will be ignored.
- Action Parameter: Sort Direction
- This parameter allows the user to provide sorting order to be applied to the application attribute provided in the Sort By parameter. It allows the comma-separated values of valid Sort Direction(s) (ASC/DESC).
- Action Parameter: Page
- This parameter allows the user to provide the index of the page from where the results are to be fetched. It expects a numeric value as an input. If not provided, then 0 will be considered as the starting index of the page.
- Action Parameter: Max Results
- This parameter allows the user to limit the number of results. If the parameter is not provided, it will fetch by default 1000 results. The internal pagination logic is applied for fetching a large number of results.
- Note:
- The Fieldname, Operator, Value, and Exclusivity parameters are used to create a filter. So, the length of these four parameters must be the same.
- Similarly, a sorting direction is required for a host attribute that is used for sorting. So, the length of Sort By and Sort Direction parameters must be the same.
- Examples:
- List the applications having a name like a “test”, sorted based on the ID in descending order.
- Fieldname = name
- Operator = LIKE
- Value = [“test”]
- Exclusivity = false
- Sort By = id
- Sort Direction = DESC
- List the applications having the group name “Default Group”. Results are sorted first by name in ascending order and then by ID in descending order.
- Fieldname = group_names
- Operator = EXACT
- Value = [“Default Group”]
- Exclusivity = false
- Sort By = name, id
- Sort Direction = ASC, DESC
- List the applications having ID 1 or 2 or 3.
- Fieldname = id
- Operator = IN
- Value = [“1,2,3”]
- Exclusivity = false
- List the applications having asset criticality in the range of 2 to 5. The maximum results to be fetched are 200.
- Fieldname = criticality
- Operator = RANGE
- Value = [“2,5”]
- Exclusivity = false
- Max Results = 200
- List the applications having a name like a test and criticality is one of 4,5,6.
- Fieldname = name,criticality
- Operator = LIKE, IN
- Value = [“test”, “4,5,6”]
- Exclusivity = false, false
List Unique Findings
- Note: RiskSense is rewriting the API which is being used for this action.
- Action Parameter: Field Name
- This parameter allows the user to filter the result data set based on the unique host finding attributes provided as input. It allows the comma-separated values of unique host finding attributes. The uid of the filter attribute must be provided here.
Here are a few examples of host attributes: title, group_names, severity, assessment_labels.
- Action Parameter: Operator
- This parameter allows the user to provide the operator which will be applied to the value(s) provided in the Fieldname parameter. It allows the comma-separated values of valid operators. The user can get the list of valid operators by executing the List Filter Attributes action.
Here are a few examples of the operators:
- EXACT - Filter records exactly matching the criteria.
- IN - Filter records matching any one of the comma-separated values.
- LIKE - Filter the records with fieldname’s value having the string provided by the user.
- RANGE - Filter the records with fieldname’s value falling in the numerical/date range provided.
- Action Parameter: Value
- This boolean parameter allows the user to provide the value of the unique host finding attributes, which is mentioned in the Fieldname parameter, to be considered for filter criteria. It expects a JSON formatted list of values.
- Action Parameter: Exclusivity
- This parameter allows the user to determine whether to fetch the results that are matching the filter criteria (defined by the Fieldname, Operator, and Value parameter) or to fetch the results that are not matching the filter criteria. It allows the comma-separated boolean values (true/false).
- Action Parameter: Sort By
- This parameter allows the user to provide the fieldname by which to sort the records. It allows the comma-separated values of valid unique host finding attributes. If multiple unique host finding attributes are provided, then multiple sorting will be applied starting from the left-most unique host finding attribute.
- Note - If an incorrect attribute value is provided in this parameter, then the sorting of the results by that attribute will be ignored.
- Action Parameter: Sort Direction
- This parameter allows the user to provide sorting order to be applied to the unique host finding attribute provided in the Sort By parameter. It allows the comma-separated values of valid Sort Direction(s) (ASC/DESC).
- Action Parameter: Page
- This parameter allows the user to provide the index of the page from where the results are to be fetched. It expects a numeric value as an input. If not provided, then 0 will be considered as the starting index of the page.
- Action Parameter: Max Results
- This parameter allows the user to limit the number of results. If the parameter is not provided, it will fetch by default 1000 results. The internal pagination logic is applied for fetching a large number of results.
- Note:
- The Fieldname, Operator, Value, and Exclusivity parameters are used to create a filter. So, the length of these four parameters must be the same.
- Similarly, a sorting direction is required for a host attribute that is used for sorting. So, the length of Sort By and Sort Direction parameters must be the same.
- Examples:
- List the unique host findings having a title like a “Solaris”, sorted based on the severity in descending order.
- Fieldname = title
- Operator = LIKE
- Value = [“Solaris”]
- Exclusivity = false
- Sort By =severity
- Sort Direction = DESC
- List the unique host findings having the Assessment “First Assessment”. Results are sorted first by title in ascending order and then by severity in descending order.
- Fieldname = assessment_labels
- Operator = EXACT
- Value = [“First Assessment”]
- Exclusivity = false
- Sort By = title, severity
- Sort Direction = ASC, DESC
- List the unique host findings having group ID 1 or 2 or 3.
- Fieldname = group_ids
- Operator = IN
- Value = [“1,2,3”]
- Exclusivity = false
- List the unique host findings having severity in the range of 2.0 to 5.0, maximum results to be fetched are 200.
- Fieldname = severity
- Operator = RANGE
- Value = [“2.0,5.0”]
- Exclusivity = false
- Max Results = 200
- List the unique host findings having a title like a “Solaris” and severity is one of 4.0,5.0,6.0.
- Fieldname = title,severity
- Operator = LIKE, IN
- Value = [“Solaris”, “4.0,5.0,6.0”]
- Exclusivity = false, false
List Host Findings
- Action Parameter: Field Name
- This parameter allows the user to filter the result data set based on the host finding attributes provided as input. It allows the comma-separated values of host finding attributes. The user can get the list of valid host finding attributes by executing the List Filter Attributes action. The uid of the filter attribute must be provided here.
Here are a few examples of host finding attributes: state, id, criticality, riskRating, assessment_labels.
- Action Parameter: Operator
- This parameter allows the user to provide the operator which will be applied to the value(s) provided in the Fieldname parameter. It allows the comma-separated values of valid operators. The user can get the list of valid operators by executing the List Filter Attributes action.
Here are a few examples of the operators:
- EXACT - Filter records exactly matching the criteria.
- IN - Filter records matching any one of the comma-separated values.
- LIKE - Filter the records with fieldname’s value having the string provided by the user.
- RANGE - Filter the records with fieldname’s value falling in the numerical/date range provided.
- Action Parameter: Value
- This parameter allows the user to provide the value of the host finding attributes, which is mentioned in the Fieldname parameter, to be considered for filter criteria. It expects a JSON formatted list of values.
- Action Parameter: Exclusivity
- This parameter allows the user to determine whether to fetch the results that are matching the filter criteria (defined by the Fieldname, Operator, and Value parameter) or to fetch the results that are not matching the filter criteria. It allows the comma-separated boolean values (true/false).
- Action Parameter: Status
- This parameter allows the user to determine whether to fetch the open host findings or the closed host findings. It expects a string value (Valid values: Open/Closed).
- Action Parameter: Sort By
- This parameter allows the user to provide the fieldname by which to sort the records. It allows the comma-separated values of valid host finding attributes. If multiple host finding attributes are provided, then multiple sorting will be applied starting from the left-most host attribute.
- Note - If an incorrect attribute value is provided in this parameter, then the sorting of the results by that attribute will be ignored.
- Action Parameter: Sort Direction
- This parameter allows the user to provide sorting order to be applied to the host finding attribute provided in the Sort By parameter. It allows the comma-separated values of valid Sort Direction(s) (ASC/DESC).
- Action Parameter: Page
- This parameter allows the user to provide the index of the page from where the results are to be fetched. It expects a numeric value as an input. If not provided, then 0 will be considered as the starting index of the page.
- Action Parameter: Max Results
- This parameter allows the user to limit the number of results. If the parameter is not provided, it will fetch by default 1000 results. The internal pagination logic is applied for fetching a large number of results.
- Note:
- The Fieldname, Operator, Value, and Exclusivity parameters are used to create a filter. So, the length of these four parameters must be the same.
- Similarly, a sorting direction is required for a host attribute that is used for sorting. So, the length of Sort By and Sort Direction parameters must be the same.
- Examples:
- List the host findings having a title like a “test”, sorted based on the ID in descending order.
- Fieldname = title
- Operator = LIKE
- Value = [“test”]
- Exclusivity = false
- Sort By = id
- Sort Direction = DESC
- List the host findings having the state “assigned”. Results are sorted first by riskRating in descending order and then by ID in ascending order.
- Fieldname = state
- Operator = EXACT
- Value = [“assigned”]
- Exclusivity = false
- Sort By = riskRating, id
- Sort Direction = DESC, ASC
- List the host findings having ID 1 or 2 or 3.
- Fieldname = id
- Operator = IN
- Value = [“1,2,3”]
- Exclusivity = false
- List the host findings having asset criticality in the range of 2 to 5. The maximum results to be fetched are 200.
- Fieldname = criticality
- Operator = RANGE
- Value = [“2,5”]
- Exclusivity = false
- Max Results = 200
- List the host findings having status “Closed” and criticality is NOT in the range of 4 to 8.
- Fieldname = criticality
- Operator = RANGE
- Value = [“4,8”]
- Exclusivity = true
- Status = Closed
List Filter Attributes
- Action Parameter: Asset Type
- Type of the asset of which the filter attributes will be fetched. Example: host, hostFinding, application, applicationFinding, tag, user.
- Examples:
- List filter attributes of host asset type.
- List filter attributes of host finding asset type.
- List filter attributes of application asset type.
Get Hosts
- Action Parameter: Host ID
- The unique host ID of the host. The Host ID is either known by RiskSense users or it can be fetched from the output of List Hosts action.
- Action Parameter: Host Name
- The hostname of the host. Host Name is either known by RiskSense users or it can be fetched from the output of List Hosts action.
- Note:
- If both the parameters (Host Name and Host ID) are provided, then the action will be executed based on the host ID.
- Examples:
- Get the host(s) having hostname “image1”
- Get the host(s) having ID “7”
- Hostname = “image1” and ID = “7”
- Host Name = image1
- Host ID = 7
Get Host Finding
- Action Parameter: Host Finding ID
- The unique host finding ID of the host finding. Host finding ID is either known by RiskSense users or it can be fetched from the output of List Host Findings action.
- Examples:
- Get the host finding having ID “6”
Get App
- Action Parameter: App ID
- The unique application ID of the application. The Application ID is either known by RiskSense users or it can be fetched from the output of List Apps action.
- Examples:
- Get the application having ID “5”
List Vulnerabilities
- Action Parameter: Host Finding ID
- The host finding ID for which the vulnerabilities are to be fetched. Host finding ID is either known by RiskSense users or it can be fetched from the output of List Hosts action.
- Examples:
- List the vulnerabilities of the host finding having ID “6”
Tag Asset
- Note: This app supports the below tag types.
- CUSTOM
- LOCATION
- COMPLIANCE
- REMEDIATION
- PEOPLE
- SCANNER
- CMDB
- Action Parameter: Tag Name
- This parameter allows the user to provide the name of an existing tag or to provide the name of a new tag, which will get associated with the assets. Users can get the list of all the available tags using the List Tags action.
- Action Parameter: Asset Type
- Type of the asset to which the tag will be applied. Example: host, hostFinding, application, applicationFinding.
- Action Parameter: Field Name
- This parameter allows the user to filter the result data set based on the asset type’s attributes provided as input. It allows the comma-separated values of the attributes. The user can get the list of valid asset types’ attributes by executing the List Filter Attributes action. The uid of the filter attribute must be provided here.
Here are a few examples: name, title, severity, rs3, riskRating, group_names, description, criticality, assessment_labels, discovered_on.
- Action Parameter: Operator
- This parameter allows the user to provide the operator which will be applied to the value(s) provided in the Fieldname parameter. It allows the comma-separated values of valid operators. The user can get the list of valid operators by executing the List Filter Attributes action.
Here are a few examples of the operators:
- EXACT - Filter records exactly matching the criteria.
- IN - Filter records matching any one of the comma-separated values.
- LIKE - Filter the records with fieldname’s value having the string provided by the user.
- RANGE - Filter the records with fieldname’s value falling in the numerical/date range provided.
- Action Parameter: Value
- This parameter allows the user to provide the value of the asset type’s attributes,
which are mentioned in the Fieldname parameter, to be considered for filter
criteria. It expects a JSON formatted list of values.
- Action Parameter: Exclusivity
- This parameter allows the user to determine whether to fetch the results that are matching the filter criteria (defined by the Fieldname, Operator, and Value parameter) or to fetch the results that are not matching the filter criteria. It allows the comma-separated boolean values (true/false).
- Action Parameter: Create New Tag
- This parameter allows the user to create a new tag if the provided tag name in the Tag Name parameter is not available on the RiskSense platform.
- Note - This parameter will only come into picture when the provided tag name is not available.
- Action Parameter: Tag Type
- Type of the new tag. This parameter is used to create a new tag.
- Note - This parameter is required when the provided tag name is not available and the Create New Tag parameter is enabled.
- Action Parameter: Tag Description
- Description of the new tag. This parameter is used to create a new tag.
- Note - This parameter is required when the provided tag name is not available and the Create New Tag parameter is enabled.
- Action Parameter: Tag Owner ID
- Owner of the new tag. This parameter is used to create a new tag. Users can get the list of all the available owner IDs using the List Users action.
- Note - This parameter is required when the provided tag name is not available and the Create New Tag parameter is enabled.
- Action Parameter: Tag Color
- Color of the new tag. This parameter is used to create a new tag.
- Note - This parameter is required when the provided tag name is not available and the Create New Tag parameter is enabled.
- Action Parameter: Propagate To All Findings
- It denotes if an asset tag should be applied to all its findings. This parameter is used to create a new tag.
- Propagate to all findings is a special boolean. If a tag is created at asset level (example: host/app level) and if the use case is to propagate those tags to associated findings also, then this parameter should be enabled. If not, it should be disabled.
- Note - This parameter is required when the provided tag name is not available and the Create New Tag parameter is enabled.
- Note:
- The Fieldname, Operator, Value, and Exclusivity parameters are used to create a filter. So, the length of these four parameters must be the same.
- Examples:
- Tag all the host findings that are in the assigned state. Tag Name = “
state assigned”.
Note- Assuming that the “state assigned” tag is already available and the tag ID is 1234.
- Tag Name = state assigned
- Asset Type = hostFinding
- Fieldname = state
- Operator = EXACT
- Value = [“assigned”]
- Exclusivity = false
- Create New Tag = false
- Tag all the hosts having rs3 value in the range of 300-400 with a tag named “high risk”. If tag is not available, create new tag with Description = “high risk alert”, Tag Type= “CUSTOM”, Tag Color= “#648d9f”, Tag Owner ID = “321”. Also, this tag should get associated with all the findings of the hosts as well.
Note- Assuming that the “high risk” tag is not available
- Tag Name = high risk
- Asset Type = host
- Fieldname = rs3
- Operator = RANGE
- Value = [“300,400”]
- Exclusivity = false
- Create New Tag = true
- Tag Type = CUSTOM
- Tag Description = high risk alert
- Tag Owner ID = 321
- Tag Color = “#648d9f”
- Propagate To All Findings = True
- Tag all the applications with the tag name “test tag”.
Note- Assuming that the “test tag” tag is already available and the tag ID is 1233.
- Tag Name = test tag
- Asset Type = application
- Create New Tag = false
Note- This will associate the tag named “test tag” to all the applications of the client (provided in the configuration parameter). Please make sure that you filter the assets correctly using the filter parameters (Fieldname, Operator, Value, Exclusivity).
- Tag all the applicationFindings with a tag named “tag application finding”
Note- Assuming that the “tag application finding” tag is not available
- Tag Name = tag application finding
- Asset Type = applicationFinding
- Create New Tag = false
Note- As the tag is not available and the user is not requesting for a new tag creation, the action will fail with a proper error message.
- Tag all the hosts having rs3 value in the range of 650-850 with a tag named “low risk”. If tag is not available, create new tag with Description = “low risk alert”, Tag Type= “CUSTOM”, Tag Color= “#648d9f”, Tag Owner ID = “321”. Also, this tag should get associated with all the findings of the hosts as well.
Note- Assuming that the “low risk” tag is already available
- Tag Name = low risk
- Asset Type = host
- Fieldname = rs3
- Operator = RANGE
- Value = [“650,850”]
- Exclusivity = false
- Create New Tag = true
- Tag Type = CUSTOM
- Tag Description = low risk alert
- Tag Owner ID = 321
- Tag Color = “#648d9f”
- Propagate To All Findings = True
Note- As the user is trying to create a tag which is already created, the tag will not get updated and the already existing tag will get associated with the filtered assets.
- Tag all the hosts having rs3 value in the range of 650-850 with a tag named “low risk”. If tag is not available, create new tag with Description = “low risk alert”, Tag Type= “CUSTOM”, Tag Color= “#648d9f”, Tag Owner ID = “321”. Also, this tag should get associated with all the findings of the hosts as well.
Note- Assuming that the “low risk” tag does not exist and there is no asset available for the provided filter related input parameter (Fieldname, Operator, Exclusivity, Value).
- Tag Name = low risk
- Asset Type = host
- Fieldname = rs3
- Operator = RANGE
- Value = [“650,850”]
- Exclusivity = false
- Create New Tag = true
- Tag Type = CUSTOM
- Tag Description = low risk alert
- Tag Owner ID = 321
- Tag Color = “#648d9f”
- Propagate To All Findings = True
Note- The new tag will not be created and won't be associated as no data is available for the provided filter inputs. The action will return an appropriate error message.


Pygame implementation of Arcade Game-Space Invaders-Group Project
A Simple Sudoku Generator and Solver made using Python
Python implementation of 2048 Game


Read this page to learn about what he/she likes (and maybe what he/she dislikes)!
Someone was recently asked about his/her top 5 movies, tv shows, and places he/her has visited. Here are his/her answers!
Here are Someone's top five favorite movies:
Here are Someone's top five favorite tv shows:
| Place Name | Picture |
|---|---|
| Museum of Modern Art | |
| The Met | |
| Central Park |