;
Issue #
Problem Name
Problem Description
Possible Solutions
Verified Solutions
Links
1
Input Output error
cannot access ‘/mnt/c’: Input/output error
wsl.exe –shutdown then Get-Service LxssManager | Restart-Service


If you care to fundraise for a charitable cause, or if you have before and want a better experience of it, please let us know. We're designing this for you, to help make a difference for all of us.
I'm Interested …


GET /invoices/api/v1/invoices
Headers
{"X-Api-Key": <invoice_key>}
Body (application/json)
Returns 200 OK (application/json)
[<invoice_object>, ...]


This article is a continuation of previous WebGL articles. The previous article was about drawing multiple things. If you haven't read them I suggest you start there.
I'm sure some CS guru or graphics guru is going to give me a ear full but ... A scene graph is usually a tree structure where each node in the tree generates a matrix... hmmm, that's not a very useful definition. Maybe some examples would be useful.
Most 3D engines use a scene graph. You put the things you want to appear in the scene graph. The engine then walks the scene graph and figures out a list of things to draw. Scene graphs are hierarchical so for example if you wanted to make a universe simulation you might have a graph that looks like this
What's the point of a scene graph? The #1 feature of a scene graph is it provides a parent child relationship for matrices as we discussed in 2d matrix math. So for example in a simple (but unrealistic) universe simualtion the stars (children), move along with their galaxy (parent). Similary a moon (child) moves along with its planet (parent) If you move the earth the moon will move with it. If you move a galaxy all the stars inside will move with it. Drag the names in the diagram above and hopefully you can see their relationships.
If you go back to the 2d matrix math you might remember we multiply lots of matrices in order to translate, rotate, and scale objects. A scene graph provides a structure to help decide what matrix math to apply to an object.
Typically each Node
in a scene graph represents a local space. Given the correct
matrix math anything in that local space can ignore everything above it. Another
way to state the same thing is that the moon only has to care about orbiting the earth.
It does not have to care about orbiting the sun. Without this scene graph structure
you'd have to do much more complex math to compute how to get the moon to orbit the sun
because it's orbit around the sun looks something like this
With a scene graph you just make the moon a child of the earth and then orbit the earth which is simple. The scene graph takes care of the fact that the earth is oribiting the sun. It does this by walking the nodes and multiplying the matrixes as it walks
worldMatrix = greatGrandParent * grandParent * parent * self(localMatrix)
In concrete terms our universe simualtion that would be
worldMatrixForMoon = galaxyMatrix * starMatrix * planetMatrix * moonMatrix;
We can do this very simply with a recursive function which is effectively
function computeWorldMatrix(currentNode, parentWorldMatrix) {
// compute our world matrix by multplying our local matrix with
// our parent's world matrix.
var worldMatrix = matrixMultiply(currentNode.localMatrix, parentWorldMatrix);
// now do the same for all of our children
currentNode.children.forEach(function(child) {
computeWorldMatrix(child, worldMatrix);
});
}
This brings up some terminalogy which is pretty common to 3d scene graphs.
localMatrix
: The local matrix for the current node. It transforms it and its children in local space with
itself at the origin.
worldMatrix
: For a given node it takes stuff in the local space of that node
and transforms it to the space of the root node of the scene graph. Or in other words it places it
in the world. If we compute the worldMatrix for the moon we'll get that funky orbit you see above.
A scene graph is pretty easy to make. Let's define a simple Node
object.
There's a zillion ways to organize a scene graph and I'm not sure which
way is best. The most common is to have an optional field of thing to draw
var node = {
localMatrix: ..., // the "local" matrix for this node
worldMatrix: ..., // the "world" matrix for this node
children: [], // array of children
thingToDraw: ??, // thing to draw at this node
};
Let's make a solar system scene graph. I'm not going to use fancy textures or anything like that as it would clutter the example. First let's make a few functions to help manage nodes. First we'll make a node class
var Node = function() {
this.children = [];
this.localMatrix = makeIdentity();
this.worldMatrix = makeIdentity();
};
Let's give it a way to set the parent of a node.
Node.prototype.setParent = function(parent) {
// remove us from our parent
if (this.parent) {
var ndx = this.parent.children.indexOf(this);
if (ndx >= 0) {
this.parent.children.splice(ndx, 1);
}
}
// Add us to our new parent
if (parent) {
parent.children.append(this);
}
this.parent = parent;
};
And here's the code to compute world matrices from local matrixes based on their parent-child relationships. If we start at the parent and recursively visit the children we can compute their world matrices. If you don't understand matrix math check out this article on them.
Node.prototype.updateWorldMatrix = function(parentWorldMatrix) {
if (parentWorldMatrix) {
// a matrix was passed in so do the math and
// store the result in `this.worldMatrix`.
matrixMultiply(this.localMatrix, parentWorldMatrix, this.worldMatrix);
} else {
// no matrix was passed in so just copy.
copyMatrix(this.localMatrix, this.worldMatrix);
}
// now process all the children
var worldMatrix = this.worldMatrix;
this.children.forEach(function(child) {
child.updateWorldMatrix(worldMatrix);
});
};
Let's just do the sun, the earth, and the moon to keep it simple. We'll of course use
fake distances so things fit on the screen. We'll just use a single sphere model
and color it yellowish for the sun, blue-greenish for the earth and grayish for the moon.
If drawInfo
, bufferInfo
, and programInfo
are not familiar to you see the previous article.
// Let's make all the nodes
var sunNode = new Node();
sunNode.localMatrix = makeTranslation(0, 0, 0); // sun at the center
sunNode.drawInfo = {
uniforms: {
u_colorOffset: [0.6, 0.6, 0, 1], // yellow
u_colorMult: [0.4, 0.4, 0, 1],
},
programInfo: programInfo,
bufferInfo: sphereBufferInfo,
};
var earthNode = new Node();
earthNode.localMatrix = makeTranslation(100, 0, 0); // earth 100 units from the sun
earthNode.drawInfo = {
uniforms: {
u_colorOffset: [0.2, 0.5, 0.8, 1], // blue-green
u_colorMult: [0.8, 0.5, 0.2, 1],
},
programInfo: programInfo,
bufferInfo: sphereBufferInfo,
};
var moonNode = new Node();
moonNode.localMatrix = makeTranslation(20, 0, 0); // moon 20 units from the earth
moonNode.drawInfo = {
uniforms: {
u_colorOffset: [0.6, 0.6, 0.6, 1], // gray
u_colorMult: [0.1, 0.1, 0.1, 1],
},
programInfo: programInfo,
bufferInfo: sphereBufferInfo,
};
Now that we've made the nodes lets connect them.
// connect the celetial objects
moonNode.setParent(earthNode);
earthNode.setParent(sunNode);
We'll again make a list of objects and a list of objects to draw.
var objects = [
sunNode,
earthNode,
moonNode,
];
var objectsToDraw = [
sunNode.drawInfo,
earthNode.drawInfo,
moonNode.drawInfo,
];
At render time we'll update each object's local matrix by rotating it slightly.
// update the local matrices for each object.
matrixMultiply(sunNode.localMatrix, makeYRotation(0.01), sunNode.localMatrix);
matrixMultiply(earthNode.localMatrix, makeYRotation(0.01), earthNode.localMatrix);
matrixMultiply(moonNode.localMatrix, makeYRotation(0.01), moonNode.localMatrix);
Now that the local matrices are updated we'll update all the world matrices
sunNode.updateWorldMatrix();
Finally now that we have world matrices we need to multiply those to get a worldViewProjection matrix for each object.
// Compute all the matrices for rendering
objects.forEach(function(object) {
object.drawInfo.uniforms.u_matrix = matrixMultiply(object.worldMatrix, viewProjectionMatrix);
});
Rendering is the same loop we saw in our last article.
You'll notice all of the planets are the same size. Let's try to make the earth larger
earthNode.localMatrix = matrixMultiply(
makeScale(2, 2, 2), // make the earth twice as large
makeTranslation(100, 0, 0)); // earth 100 units from the sun
Oops. The moon got larger too. To fix this we could manually shrink the moon. A better solution though is to add more nodes to our scene graph. Instead of just
sun
|
earth
|
moon
We'll change it to
solarSystem
| |
| sun
|
earthOrbit
| |
| earth
|
moonOrbit
|
moon
This will let the earth rotate around the solarSystem but we can separately rotate and scale the sun and it won't
effect the earth. Similarly the earth can rotate separately from the moon. Let's make more nodes for
solarSystem
, earthOrbit
and moonOrbit
.
var solarSystemNode = new Node();
var earthOrbitNode = new Node();
earthOrbitNode.localMatrix = makeTranslation(100, 0, 0); // earth orbit 100 units from the sun
var moonOrbitNode = new Node();
moonOrbitNode.localMatrix = makeTranslation(20, 0, 0); // moon 20 units from the earth
Those orbit distances have been removed from the old nodes
var earthNode = new Node();
-earthNode.localMatrix = matrixMultiply(
- makeScale(2, 2, 2), // make the earth twice as large
- makeTranslation(100, 0, 0)); // earth 100 units from the sun
+earthNode.localMatrix = makeScale(2, 2, 2); // make the earth twice as large
var moonNode = new Node();
-moonNode.localMatrix = makeTranslation(20, 0, 0); // moon 20 units from the earth
Connecting them now looks like this
// connect the celetial objects
sunNode.setParent(solarSystemNode);
earthOrbitNode.setParent(solarSystemNode);
earthNode.setParent(earthOrbitNode);
moonOrbitNode.setParent(earthOrbitNode);
moonNode.setParent(moonOrbitNode);
And we only need to update the orbits
// update the local matrices for each object.
-matrixMultiply(sunNode.localMatrix, makeYRotation(0.01), sunNode.localMatrix);
-matrixMultiply(earthNode.localMatrix, makeYRotation(0.01), earthNode.localMatrix);
-matrixMultiply(moonNode.localMatrix, makeYRotation(0.01), moonNode.localMatrix);
+matrixMultiply(earthOrbitNode.localMatrix, makeYRotation(0.01), earthOrbitNode.localMatrix);
+matrixMultiply(moonOrbitNode.localMatrix, makeYRotation(0.01), moonOrbitNode.localMatrix);
// Update all world matrices in the scene graph
-sunNode.updateWorldMatrix();
+solarSystemNode.updateWorldMatrix();
And now you can see the earth is double size, the moon is not.
You might also notice the sun and the earth are no longer rotating in place. That is now independent.
Let's adjust a few more things.
-sunNode.localMatrix = makeTranslation(0, 0, 0); // sun at the center
+sunNode.localMatrix = makeScale(5, 5, 5);
...
+moonNode.localMatrix = makeScale(0.4, 0.4, 0.4);
...
// update the local matrices for each object.
matrixMultiply(earthOrbitNode.localMatrix, makeYRotation(0.01), earthOrbitNode.localMatrix);
matrixMultiply(moonOrbitNode.localMatrix, makeYRotation(0.01), moonOrbitNode.localMatrix);
// spin the sun
matrixMultiply(sunNode.localMatrix, makeYRotation(0.005), sunNode.localMatrix);
+// spin the earth
+matrixMultiply(earthNode.localMatrix, makeYRotation(0.05), earthNode.localMatrix);
+// spin the moon
+matrixMultiply(monNode.localMatrix, makeYRotation(-0.01), moonNode.localMatrix);
Currently we have a localMatrix
and we're modifying it each frame. There's a problem though
in that every frame our math will collect a little bit of error. There are ways to fix the math
which is called ortho normalizing a matrix but even that won't always work. For example let's
imagine we scaled down zero and back. Let's just do that for one value x
x = 246; // frame #0, x = 246
scale = 1;
x = x * scale // frame #1, x = 246
scale = 0.5;
x = x * scale // frame #2, x = 123
scale = 0;
x = x * scale // frame #3, x = 0
scale = 0.5;
x = x * scale // frame #4, x = 0 OOPS!
scale = 1;
x = x * scale // frame #5, x = 0 OOPS!
We lost our value. We can fix this by adding some other class that updates the matrix from
other values. Let's change the Node
definition to have a source
. If it exists we'll
ask the source
to give us a local matrix.
*var Node = function(source) {
this.children = [];
this.localMatrix = makeIdentity();
this.worldMatrix = makeIdentity();
+ this.source = source;
};
Node.prototype.updateWorldMatrix = function(matrix) {
+ var source = this.source;
+ if (source) {
+ source.getMatrix(this.localMatrix);
+ }
...
Now we can create a source. A common source is one that provides translation, rotation, and scale something like this
var TRS = function() {
this.translation = [0, 0, 0];
this.rotation = [0, 0, 0];
this.scale = [1, 1, 1];
};
TRS.prototype.getMatrix = function(dst) {
dst = dst || new Float32Array(16);
var t = this.translation;
var r = this.rotation;
var s = this.scale;
// compute a matrix from translation, rotation, and scale
makeTranslation(t[0], t[1], t[2], dst);
matrixMultiply(makeXRotation(r[0]), dst, dst);
matrixMultiply(makeYRotation(r[1]), dst, dst);
matrixMultiply(makeZRotation(r[2]), dst, dst);
matrixMultiply(makeScale(s[0], s[1], s[2]), dst, dst);
return dst;
};
And we can use it like this
// at init time making a node with a source
var someTRS = new TRS();
var someNode = new Node(someTRS);
// at render time
someTRS.rotation[2] += elapsedTime;
Now there's no issue because we are recreating the matrix each time.
You might be thinking, I'm not making a solar system so what's the point? Well, If you wanted to animate a human you might have a scene graph that looks like this
How many joints you add for fingers and toes is up to you. The more joints you have the more power it takes to compute the animations and the more animation data it takes to provide info for all the joints. Old games like Virtua Fighter had around 15 joints. Games in the early to mid 2000s had 30 to 70 joints. If you did every joint in your hands there's at least 20 in each hand so just 2 hands is 40 joints. Many games that want to animate hands animate the thumb as one and the 4 fingers as one large finger to save on time (both CPU/GPU and artist time) and memory.
In any case here's a block guy I hacked together. It's using the TRS
source for each
node mentioned above. Programmer art and programmer animation FTW! :P
If you look at pretty much any 3d library you'll find a scene graph similar to this.


SPLICE Support
The SPLICE team gratefully acknowledges the support provided by the National Science Foundation.
- Core R&D Programs DLR-1740775 DLR-1740798 DLR-1740765 supports the collaboration of University of Pittsburgh, CMU, and Virginia Tech. See the 2017 NSF Grant Proposal (funded beginning September 2017).
The SPLICE team gratefully acknowledges the support provided by Technology-enhanced Learning and Online Strategies (TLOS). In particular, TLOS supported development of the LTI tutorials and associated documentation at this website.


MCMS Admin
Sign in to your account
Please enter your name and password to log in.
Forget Password?
Enter your e-mail address below to reset your password.
2005 © Net-Tomorrow LTD.
{% extends '../layoutNoLogin.html' %} {% block title %}Login{% endblock %} {% block content %}
Please enter your name and password to log in.
Enter your e-mail address below to reset your password.


Log in
Get the best movie recommendations and keep track of your movie watching history.
{% include 'components/login-form.html' %}{% extends 'base.html' %} {% load static %} {% block body %}
{% include 'components/top-app-bar.html' %}Get the best movie recommendations and keep track of your movie watching history.
{% include 'components/login-form.html' %}


Welcome to our on-line pizza shop!
Please choose one or more toppings for your pizza:
cheese
pepperoni
artichoke
anchovy
mushrooms
veggies
chicken
Please choose your pizza size:
small
medium
large
Confirm Pizza Order
Thank you for your order!
Your pizza price is: $
.
You ordered a
pizza


Explanation of STEP1 - Co-ideation
Please add your input in each box, and rate others’ contributions. Your input will help convince service providers to convert your ideas into long term care services.
Please add your input in each box, and rate others’ contributions. Your input will help convince service providers to convert your ideas into long term care services.
Please sign in
or register and you will be able to create and propose topics relevant to you , others will then join you to share their personal experience.
POSTS
No comment the moment !
Use the form below and be the first to comment this topic !
Use the form below and be the first to comment this topic !


Themes and colours¶
As mentioned before, friendly uses Rich to add colours. Syntax colouring is done by Rich using Pygments. While Pygments comes with many different styles (colour schemes), most of them do not define colours for all possible parts of a Python traceback: depending on the style, we sometimes end up with some text with the same colour as the background.
To ensure that all of friendly’s output would be styled properly, friendly includes its own “themes”: one suitable for light coloured backgrounds, and one for dark coloured backgrounds. One problem I had was to figure out all the possible styling elements. It turned out that this problem had bee “solved” in 2008 when Johannes Woolard and I created the Pygments Tango style for an old project where we sought to include all possible styling elements, while minimizing the numbers of colours used.
Designing a pygments colour style is one thing; having it faithfully displayed in a terminal is something else altogether. Below you will see various screenshots: the first one is taken using the new Windows Terminal. Other screenshots have been taken using ConEmu, using different colour schemes available from ConEmu’s settings. Much to my surprise, even though the colours I have chosen are not standard colours, they are much altered by ConEmu depending on the chosen colour scheme.
friendly default theme using Windows Terminal¶
ConEmu: base16 theme¶
ConEmu: default windows theme¶
ConEmu: powershell theme¶
Other OS¶
Screenshots taken by MacOS or Linux users would be welcome.
Rich not supported¶
Rich works by adding escape sequences which are interpreted by terminals as adding style (colours, font style like bold, italics, or underlined, etc.). Some environment cannot interpret these escape sequences. Here is what happens if we attempt to use Rich together with Python’s IDLE for the same code as shown above:
Conclusion¶
While suggestions for improving friendly are generally always welcome, suggested changes to the current default theme will likely be ignored since the end result appear to be completely dependent on the environment.
I might consider supporting custom themes, but this will likely
be a lower priority item: chances are that using either the
'light'
or 'dark'
theme with a custom background
colour will be sufficient in most situations for the time being.


| Created: | 6/27/2020 6:52:06 AM |
| Modified: | 6/27/2020 6:52:06 AM |
| Project: | |
| Advanced: |
| Attribute |
|
Public serial id |
|
Details:
|
|
Public integer receipt_id |
|
Details:
|
|
Public integer supplier_id |
|
Details:
|
|
Public varchar(255) description |
|
Details:
|
|
Public date deposit_date |
|
Details:
|
|
Public date processing_date |
|
Details:
|
|
Public bigint amount_cents |
|
Details:
|
|
Public bigint federal_amount_cents |
|
Details:
|
|
Public bigint non_federal_amount_cents |
|
Details:
|
|
Public varchar(255) created_by |
|
Details:
|
|
Public varchar(255) updated_by |
|
Details:
|
|
Public timestamp with time zone(0) created_at |
|
Details:
|
|
Public timestamp with time zone(0) updated_at |
|
Details:
|
|
Public timestamp with time zone(0) archived_at |
|
Details:
|
|
Public varchar(255) rejection |
|
Details:
|
| Operation | ||
|
Public receipt_lines_pkey( id: serial, |
||
|
Details:
<<PK>>
|
||
|
Public receipt_lines_receipt_id_foreign( receipt_id: integer, |
||
|
Details:
<<FK>>
|
| Element | Source Role | Target Role |
|
«table» receipts Table «FK» |
Name: receipt_lines_receipt_id_foreign |
Name: receipts_pkey |
|
Details:
|
| Element | Source Role | Target Role |
|
«table» receipt_line_buckets Table «FK» |
Name: receipt_line_buckets_receipt_line_id_foreign |
Name: receipt_lines_pkey |
|
Details:
|
||
|
«table» distribution_lines Table «FK» |
Name: distribution_lines_receipt_line_id_foreign |
Name: receipt_lines_pkey |
|
Details:
|
||
|
«table» receipt_line_buckets Table «FK» |
Name: receipt_line_buckets_receipt_line_id_foreign |
Name: receipt_lines_pkey |
|
Details:
|
||
|
«table» distribution_lines Table «FK» |
Name: distribution_lines_receipt_line_id_foreign |
Name: receipt_lines_pkey |
|
Details:
|
| Tag | Value |
| Owner | public |
|
Details:
|
| Property | Value |
| isFinalSpecialization: | 0 |


The posts will be the heart and soul of your (and any) blog. Therefore, I have made an extra effort while writing the code for the posts.
Yellowblue's posts, apart from the basic features, provide you with some extra features which make the overall navigating and reading experience, a pleasant and effortless process.
Some of the posts' features, are:
Writing posts in Jekyll requires you to know a little about about Front Matter. Don't worry though; even a quick read through Jekyll's documentation about Front Matter, will get you up and running in no time.
Now, the actual process of writing posts ia also very well documented. Please make sure to read both about Front Matter and writing posts, in order to get a solid grasp on writing posts in Jekyll.
The necessary variables for a post, are the layout, the title and the date. Below you can see a basic post:
---
layout: post
title: "Welcome to Yellowblue!"
date: 2012-06-16 18:19:27
---
Post body goes here
Note that the post body can be written in Markdown, HTML, or even in both of them.
The best way to get an idea about how posts are written, is to just check the theme's posts in the _posts
folder.
Permalinks can be used in Yellowblue, as in any Jekyll site. Again, Jekyll provides detailed documentation about how to use permalinks. Just make sure that each post has a unique permalink!
If you have an image, say my_hero_image.jpg
and want to use it as a hero image for your post, the first thing to do is copy the image into the images
folder.
If you want a lower resolution version of the image, say my_hero_image_low_res.jpg
, to appear in the post's teaser place the image into the images
folder.
If you want the image to link to a larger image, place in the images
folder a larger version of the image, say my_hero_image_large.jpg
.
A post with a hero image, will look like this:
---
layout: post
title: "Welcome to Yellowblue!"
date: 2012-06-16 18:19:27
hero: images/my_hero_image.jpg
hero_high: images/my_hero_image_large.jpg
hero_low: images/my_hero_image_low_res.jpg
hero_alt: My Hero Image
---
Post body goes here
As you can see, the variables regarding hero images, are the following:
| Variable | Value |
|---|---|
| hero | The path to the image file |
| hero_high | The path to the image file of a high resolution version. The image will be used as a link from the original hero image. |
| hero_low | The path to the image file of a low resolution version. The image will be used in the post teaser. |
| hero_alt | The alternative text to the image. It will be included in the images markup. |
Yellowblue uses Disqus, a widely popular comments service. In order to you use it, you have to create an account there.
By default, comments in the YB theme are disabled and you get to determine if a post will accept comments or not.
If you want to have the comments enabled by default, just head over to _config.yml
and change the line comments: false
to comments: true
.
If you want to have the comments disabled by default, but you want to choose which posts will allow comments, just add the line comments: true
in your post's Front Matter section.
If you want to have the comments enables by default, but you want to choose which posts will not allow comments, just add the line comments: false
in your post's Front Matter section. Also make sure that in _config.yml
the comments
variable is set to true
.
The code for the comments resides in _includes/comments.html
. The code is provided by Disqus and the comments (for the code) are quite explanatory. All you need to change, is the Disqus username. Yelloblue's username is yellowblueeu
, so all you have to do in the following piece of code:
var disqus_shortname = 'yellowblueeu'; // required: replace example with your forum shortname
is to change yellowblueeu
with your own Disqus username. And that's it. Now your site can support comments!


Are you looking to gain 1-on-1 advice, mentorship or guidance on your company culture, customer service, or human resource journey? We have a seasoned group of professionals who are ready and equipped to help you.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.


Fill in the basic information for a list and make the request to SharePoint. The xml response will appear at the bottom of the page where you can then copy by Ctrl + A.
[0 = All Items]
Operation to query with.
Leaving this blank will return all fields visible in the default list view.


A shape that looks like a flattened circle.
It can obtained by making a slanting cut through the side of a cone.
Shapes that look like an ellipse are said to be elliptical.


Indeed
CareerBuilder
Snag
ZipRecruiter
Craigslist
Kansasworks
Workforce Centers
Associated General Contractors


Intervention Series. (2010 - Ongoing). Diverse media.
The project ‘Nem. – ‘let’s go’ in the local dialect – took its cue from the geological isolation of Oggiogno’s 16 inhabitants started in 2010.
‘Nem.’s first intervention consisted of a series of invitations to a non-resident public to walk towards Oggiogno through the mountain path connecting the village to public services. A central aim being to amplify how the mountain path functioned in that moment in time as a physical platform in which the exchange of information regarding the crisis was taking place.
‘Nem.’s second intervention started in 2013 and it is ongoing. An aluminium time capsule travels the houses of the inhabitants of Oggiogno. Aluminium was chosen as a material because its resilience exemplifies the status of the village through qualities such as resistance and strength. Each host decides to hold the capsule for a variable amount of time. While hosted, the capsule stratifies not only ephemeral contents (i.e. the scent of a fireplace), time and affectivity but it also forms a portrait of the contemporary history of Oggiogno. In this framework, the capsule operates as nomadic-micro-platform.
The outcome of this intervention is an ongoing photo series and a publication foreseen for 2019.


Casablanca
A film by Michael Curtiz
Starring Humphrey Bogart, Ingrid Bergman, and Claude Rains
By now, this movie has transcended even film itself. I was a late = bloomer: it was a long time until I saw Casablanca. Too bad, because = when it was all said and done, I thought this really was the beginning = of a beautiful friendship. If you are one of those extremely rare = people who have never seen this gorgeously amazing film, go right now = and rent it. Then watch it again. And again. And again. It's that = good. =20 This, simply, is the best romance Hollywood has ever concocted. It = just might be the best picture Hollywood has ever made. Alright, = alright, I'm jumping ahead of myself. Let's start at the beginning. = Rick Blaine (Humphrey Bogart) is a bar owner in Casablanca, a travel = town in Morocco during WWII. It is controlled by the Vichy French = Government, but Rick is usually given a free hand to do what he pleases. = No one knows what fully goes on in Rick's place but Rick himself, as = visas are sold, bribes are issued, and a whole host of other things go = on. It is a normal night, with many many people trying to flee = Casablanca to America. The plot centers around one of these people: = Victor Laszlo, a French Resistance leader. He and his wife Elsa = (Bergman) come to Casablanca to seek visas to America. =20 The catch? Elsa is an old flame of Rick. She used to date him, and = they frequented a bar with a black piano player named Sam (the = incomparable Dooley Wilson), who came with Rick to set up shop in = Casablanca. Elsa dumped Rick on a rainy night in Paris, and Rick's = heart has been stone-cold ever since. Rick holds two visas with him = that could save the lives of the Laszlos, but he waits, for he feels he = shouldn't give them to Laszlo at any price. Finally, after the pleas of = Elsa, Rick concocts a plan to get her out of the country. Bogart and Bergman are simply fabulous in their respective roles. = Claude Rains playes police captain Louis Renault to absolute perfection. = He is marvelously hilarious, sharing some memorable scenes with Bogart, = especially the final scene. The direction is subtly perfect by Curtiz, = and everything comes together marvelously. Nothing in this film goes = wrong, and if it does, who cares? For all the inconsistencies in the = script (fog in Morocco? visas that can't be rejected by the Nazis?), = the lines are so good that they make up for it. "Play it again, Sam". = That's what we want most of all. After all, "a kiss is just a = kiss....as time goes by". The script ends up to be marvelous. This is = as close to flawless as Hollywood will ever get. =20 How can you argue with Bogie? You can't. Watch Casablanca again. = It'll be the start of a beautiful friendship.
RATING (out of 4): **** (2nd best movie I've ever seen (only to the Godfather))
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Spark Service Bureaus Sample App
Log in
Upload
Get quotes
Submit model
×
Spark Sample App
This is an open source Drive API demo sample app.


South Korea said it would send its top national security adviser to Pyongyang this week to discuss denuclearization and ways to improve inter-Korean relations, pushing engagement efforts even as the U.S. remains wary of talking to the nuclear-armed state.
Read moreChinese and U.S. officials will soon reconvene discussions on trade disputes, a senior Chinese official said, amid concerns that Trump administration tariffs on steel and aluminum may pitch the world’s largest economies toward a trade war.
Read moreMr. Kelly, President Trump’s chief of staff, backed up the F.B.I. director’s statement that information about Mr. Porter had been delivered to the White House last March..
Read moreMajor retailers have pledged to stop selling certain assault-style rifles and raise age requirements. But the potential effects are difficult to discern because sales data is limited.
Read moreSYRACUSE, NY -- With portions of upstate New York under a winter storm warning, National Grid offers the following tips to help customers be prepared and stay safe.
Read more


Gin&Sugary
Menu
Home
About
Posts
Contact
Tokyo Trip
Posted by
Xiaofeng Cai
on February 26, 2019 ·
49 1 min read
Day 1
Arrive
Day 2
Disney Land
Day 3
镰仓
Day 4
大涌谷
← Previous
Post


Scooby… Dooby… Do..
And I would’ve gotten away with it, too, if it weren’t for your meddling code…
04 December 2020
Problem Solving
This week was an interesting one for me. I really enjoyed working through the kata’s, getting stuck, working towards a solution..., and BAM! You try a bit of code and it works! WooHoo!
But not only did I have to face the challenges of Javascript, but also the challenge of dislocating my shoulder. Ouchies. (It’s the fourth time it’s happened, so it happens pretty easily now.)
Funnily enough though, there are some similarities between dislocating your shoulder and getting blocked on a coding challenge. You have that initial “Oh cr*p” moment, and then you have to breathe, stop and think, ok, this has happened, what are my next steps. The solution to the problem is getting to the hospital, but there are a bunch of smaller steps that need to be taken first in order to achieve this goal. So you need a plan. I dislocated my shoulder at the pool while putting on my t-shirt after a swim (I told you it happens easily), so first of all I needed to get a lifeguard, then I needed to take of my t-shirt which was only half on, then get someone to go to my car to get my phone so that I could tell my girlfriend to meet me at the hospital. I then needed the lifeguard to drive my car to the hospital. Lots of steps to go through, all while thinking “OH F…….”
If there’s anything to be learnt from this experience, it’s that solving a problem requires calm, and quite often, help from others.
So when it came to finding Scooby, it required a lot of calm when I thought “oh cr*p”. I honestly had no idea where to begin. Hold up, what about console.logging? Let's take a look at what's coming through here. Right, an array. And what's in the array? An object? Ok let's Pseudocode and write down what to do from here. Now what about .find()? Lets try some googling?
Eventually, after a fair amount of research, guided by an understanding of exactly what I wanted to achieve, thanks to Pseudocode and rubber ducking, I wrote a piece of code that console.logged the ‘Scooby’ objects. From there it was a simple if statement to grab the door number.  Just like when the shoulder goes back in :D
Reflect on how confident you feel using the problem solving techniques and process:
Pseudocode
Love it. Every time I face a challenge I begin by writing some Pseudocode. I even put pen to paper from the most part because I’m old school like that.
Trying something
Always give something a try. It may not work at all, it may work in part, or it may be the solution. You won’t know until you try.
Rubber ducky method
I don’t have a rubber duck, but I do have a tiny plastic mouse holding a lightbulb. He’s great, we’re pals.
Reading error messages
Absolutely. Sometimes they can seem like gibberish, but for the most part, they let me know my syntax is wrong
Console.logging
Love love LOVE!
Googling
Ask JeevesHow good. If you’ve got a problem, someone else has already solved it and posted about it online.
Asking your peers for help
We are all in this together, so we can all help each other learn. Everyone sees things differently, so we can all benefit from another's perspective
Asking coaches for help
I’m gonna rely on this a lot during bootcamp I think, but for now I’m trying to get cosy with most other techniques.
Improving your process with reflection
It can be hard to spend ample time reflecting at the moment, although I have been having some coding dreams lately. I’m really looking forward to having a good amount of time to reflect in the time before bootcamp.


Sipcoin Plans
Lend
$1010 - $10000- Daily Returns
- Up to 42% Monthly +
0.1% Fixed Daily - Capital Release - 7 Months
Lend
$10010 - $50000- Daily Returns
- Up to 42% Monthly +
0.15% Fixed Daily - Capital Release - 5 Months
Lend
$50010 - $100000- Daily Returns
- Up to 42% Monthly +
0.2% Fixed Daily - Capital Release - 4 Months


PHOTOS: Black Stars hold first training in São Tomé ahead 2021 AFCON qualifier
The Black Stars held their first training in São Tomé and Principe ahead their 2021 Africa Cup of Nations qualifier on Monday.
The Black Stars have touched down in São Tomé on Sunday after ahead of their second 2021 Africa Cup of Nations Group C clash on Monday.
Kwesi Appiah’s men plunged into training just hours after landing at the match venue — Stade Nacional 12 de Julho.
The match is scheduled to come off at 01:00 GMT.
Check out pictures of the training below;


GitHub issues resolved for v3.2.3
As part of this release 557 issues were closed.
--MSL-general--
Documentation
- #1747 HTML conventions are not followed for strong/emphasis
- #1991 Lots of new HTML errors in MSL v3.2.2 release
- #2513 (PR) Fixed documentation links
- #2517 (PR) Remove all occurrences of valign="top" from Documentation
- #2580 (PR) Fix HTML tags and typo
- #2584 (PR) Switch to secure website for haumer.at
- #2703 (PR) Fix typos
- #2756 (PR) Update doc.modelica.org: Add symlink to keep the new structure backwards compatible
Miscellaneous
- #2178 (PR) Remove deprecated Text-attributes
- #2187 (PR) Issue #2161 contributing
- #2320 Implement License change decision to change to BSD-3-Clause
- #2373 (PR) Merge #2320 license aka Change to 3-Clause BSD License
- #2525 (PR) Fixing typos and unwanted changes in several packages
- #2587 (PR) Check file encoding and language standard
- #2741 Tool regression in regression runs for MSL v3.2.3-rc.1
- #2783 Analysis of the MSL v3.2.3-rc.1+71590c7 regressions vs. v3.2.2+build.0-beta.3
- #2787 Set copyright holder to Modelica Association everywhere
- #2806 (PR) Set copyright holder consistently
- #2809 Analysis of the MSL v3.2.3-rc.2 regressions vs. v3.2.2+build.0-beta.3
- #2811 (PR) Update copyright year to 2019
Blocks
Bugs
- #1899 ModelicaStandardTables_*_read handling is fragile
- #2080 Problem with CombiTimeTable
- #2100 Missing obsolete annotation
- #2102 Modelica.Blocks.Sources.Exponentials should be a block
- #2140 Initial condition of SlewRateLimiter
- #2508 Minimum value of t_eps in blocks ContinuousMean, Variance and StandardDeviation
- #2724 Broken table-interpolation?
Enhancements
- #477 Interpolation options
- #1627 CombiTimeTable does not generate time events
- #1771 Wrong CombiTimeTable output when startTime < first table point
- #1839 CombiTable1D/CombiTable2D extrapolate linearly when setting ConstantSegments
- #1996 Argument of harmonic
- #2064 Add new block RealFFT with examples
- #2079 Parameter enableNoise depends per default on settings in GlobalSeed
- #2120 Blocks.Tables lack of functionality / functions
- #2190 Add periodic continuation for BooleanTable and IntegerTable
- #2191 Add blocks for inverse of log2 and log10
- #2192 Move file I/O of ModelicaStandardTables to ModelicaIO
- #2221 (PR) Added Power block and generalized Log block
- #2244 ModelicaStandardTables: Add warning option for extrapolation
- #2255 (PR) Generalize Multiplex/DeMultiplex for arbitrary number of connector signals
- #2263 (PR) UseTimeEventsInstead
- #2311 Remove
import Modelica;
- #2316 Add Integrator block with external reset trigger
- #2319 (PR) Add optional reset to Integrator and LimIntegrator
- #2321 Add bivariate table block with n inputs and n outputs
- #2344 (PR) Make use of groupImage to help understanding block parameters
- #2363 (PR) Improve switch icon visualization
- #2382 Improve Modelica.Blocks.Math.WrapAngle
- #2390 (PR) Add bivariate table block with vectorized inputs and vectorized output
- #2398 (PR) Move timeScaled computation in TimeTable to equation section
- #2419 (PR) Unify location of %name in icon view of Blocks.Interfaces
- #2471 (PR) Change proposal to show calculation equation in icon of Division
- #2489 Add blocks to calculate total harmonic distortion (THD)
- #2526 LimPID with feed-forward
- #2535 (PR) THD implementation of #2489
- #2713 (PR) Fix false extent of text "name" in icon
Examples
- #1975 Not quite 90 degrees, in Modelica.Mechanics.Rotational.Examples.CoupledClutches
- #2522 (PR) Add missing StopTime annotations to examples
Documentation
- #1982 Documentation still refers to ModelicaAdditions
- #2123 Question on comments of discrete interface blocks
- #2169 Fix documentation of CombiTable1D, CombiTable1Ds and CombiTable2D
- #2203 Documentation of Modelica.Blocks describes scalars as vectors
- #2246 ModelicaStandardTables: Document index search strategy
- #2256 Awkward wording in RS Flip Flop description
- #2257 Wording suggestion for Modelica.Blocks.Logical.Timer
- #2261 (PR) Adding tags to terms
- #2265 (PR) Improve documentation of Blocks
- #2322 Reference to very old Dymola versions in MSL documentation: remove all tool specific documentation from MSL
- #2334 (PR) Ref #2164: Remove misleading promise of future change
- #2345 (PR) Remove outdated tool references for issue #2322
- #2495 Documentation refers to non existing parameter startTime in Modelica.Blocks.Math.ContinuousMean, Variance and StandardDeviation
- #2540 (PR) #2495 fixed (documentation corrected: replaced startTime by <simulation start time>)
- #2579 (PR) Fix image and class links
Miscellaneous
- #1835 Rename pulsStart of BooleanPulse
- #2044 Relational Blocks describe input as Boolean
- #2067 Modelica.Blocks.Nonlinear.VariableDelay should declare delayMax as duration
- #2160 (PR) Fixed issue #2079 - enableNoise in PartialNoise depends on GlobalSeed
- #2175 Blocks.Tables.CombiTable1Ds seems inconsistent
- #2188 PartialBooleanBlock rectangle line too thick?
- #2209 TimeTable does not assert that first time value is 0
- #2237 %name field missing in Modelica.Blocks.Logical
- #2271 (PR) Discrete blocks should not have continuous connectors
- #2353 (PR) Add missing
each
in Modelica/Blocks/Math.mo
- #2435 Literal double value output by omc exceeds DBL_MAX
- #2502 Unclear parameter description in Add and Add3
- #2532 (PR) Extend obsolete classes from ObsoleteModel
- #2561 (PR) Added more options for homotopy-based initialization of limiters
- #2611 Diagram elements of Multiplex / DeMultiplex should be empty
- #2613 (PR) Fix icon / diagram graphics of Mux / Demux blocks
- #2643 (PR) Extend function icon for padeCoefficients2
- #2729 Field %name written twice on several blocks
- #2732 (PR) Fix double %name in icons of Blocks and ComplexBlocks
- #2757 Icons for Blocks.Logical (LessThreshold, LessEqualThreshold, GreaterThreshold and GreaterEqualThreshold) misleading when flipped
- #2758 (PR) Fix icons to utilize graphics instead of text
C-Sources
Bugs
- #1899 ModelicaStandardTables_*_read handling is fragile
- #1962 Capitalization of windows.h for cross compilation
- #1976 createDirectory fails on existing directory
- #2001 ModelicaMatIO not compatible with hdf5 1.10
- #2008 Make ModelicaIO.h usable from a C++ environment
- #2040 Restarted simulation of CombiTimeTable with periodic extrapolation can give wrong results
- #2052 No header(s) for ModelicaExternalC library
- #2069 Resource leak in ModelicaRandom_impureRandom_xorshift1024star
- #2074 Fix module constructor/destructor (in ModelicaExternalC/ModelicaStandardTables) if compiled as C++
- #2080 Problem with CombiTimeTable
- #2094 Buildscripts for zlib
- #2097 Fix uthash_fatal
- #2119 Fix error handling if variable is not found in MAT-file (ModelicaStandardTables/ModelicaIO)
- #2233 Wrong extrapolation of CombiTimeTable if simulation start time equals t_max
- #2235 Incorrect use of putenv in ModelicaInternal.c on modern macOS
- #2295 calloc(0, x) not well defined
- #2310 Modelica C-Sources on dSPACE
- #2387 Access violation for Modelica.Utilities.Files.list on 64-bit Windows
- #2396 Access violation in ModelicaExternalC
- #2725 (PR) Fix event detection and left extrapolation of CombiTimeTable
Enhancements
- #477 Interpolation options
- #1627 CombiTimeTable does not generate time events
- #1771 Wrong CombiTimeTable output when startTime < first table point
- #1839 CombiTable1D/CombiTable2D extrapolate linearly when setting ConstantSegments
- #2092 Tables/Matrices: Update Matio Library to v1.5.12
- #2095 Update zlib to v1.2.11
- #2105 Improve error message for reading MATLAB structure variables
- #2106 Support single-precision arrays from MAT-file for ModelicaMatIO
- #2120 Blocks.Tables lack of functionality / functions
- #2151 Warning if not all available data is read into a CombiTable
- #2159 (PR) Add support for integer and single
- #2192 Move file I/O of ModelicaStandardTables to ModelicaIO
- #2244 ModelicaStandardTables: Add warning option for extrapolation
- #2262 (PR) Utilize hash macros of uthash.h v2.0.2 for ModelicaStrings_hashString
- #2404 Text file format of external input data sets
- #2411 Improve reentrancy of table blocks
- #2428 (PR) Ignore UTF-8 BOM of text file for table blocks
- #2708 (PR) Add format attributes to functions in ModelicaUtilities
Documentation
- #2073 Document Visual Studio linker optimization options for ModelicaExternalC and ModelicaStandardTables
- #2246 ModelicaStandardTables: Document index search strategy
Miscellaneous
- #2216 (PR) Restructure ModelicaExternalC sources
- #2250 Use of CPL1.0 license in ModelicaStrings.c without proper declaration
- #2369 (PR) Workaround for dummy usertab function
- #2531 (PR) Avoid MSVC compiler warnings C4267 in ModelicaFFT.c
- #2656 (PR) Keep snprintf.c as stand-alone module
- #2676 (PR) Correct misleading error message when out of string memory for ModelicaInternal_readLine
Complex*
Bugs
- #1822 Why is the Complex library Protected?
- #2177 Modelica.ComplexBlocks.Interfaces.ComplexSI2SO is wrong
- #2205 ComplexBlocks.Math.Feedback uses wrong useConjugateInput
- #2449 LogFrequencySweep does not work correctly if time<0
- #2537 Change parameter limit of Modelica.ComplexBlocks.Sources.ComplexRampPhasor
Enhancements
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2383 Add variable of angle in Modelica.ComplexBlocks.Sources.ComplexRotatingPhasor
- #2450 Add complex ramp phasor source
- #2452 Restriction of wMin < wMax is technically not required for LogFrequencySweep
- #2454 Complex replicator is missing in ComplexBlocks
- #2473 Add block to simplify plotting of Bode diagrams
Examples
- #2761 Missing component descriptions in example ShowTransferFunction
- #2767 (PR) Add component descriptions to example Modelica.ComplexBlocks.Examples.ShowTransferFunction
Documentation
- #2168 Fix documentation of ComplexMath.Asin, Acos and Log
- #2265 (PR) Improve documentation of Blocks
- #2285 Complex library does not contain copyright and license information
Miscellaneous
- #2166 Missing comments for ComplexMath.TransferFunction and ShowTransferFunction
- #2167 Improve comment of ComplexMath.Log
- #2293 Irregular colors used in QuasiStationary packages
- #2504 (PR) Fixes #1822 by removing the Protection annotation and bump version
- #2729 Field %name written twice on several blocks
- #2732 (PR) Fix double %name in icons of Blocks and ComplexBlocks
Constants
Enhancements
- #2303 Add elementary charge of electron to Modelica.Constants
- #2351 (PR) Add elementary charge
Electrical.Analog
Bugs
- #1871 Why start value for Modelica.Electrical.Analog.Interfaces.ConditionalHeatPort.heatPort.T?
- #2031 Modelica.Electrical.Analog.Basic.Inductor, Transformer, etc. render poorly on non-white backgrounds
- #2070 Modelica.Electrical.Analog.Lines: OLine, ULine differ from documentation
- #2147 Duplicated function pow in Modelica.Electrical.Analog.Semiconductors
- #2270 IdealizedOpAmpLimted has issues
- #2308 Connector descriptions are partly missing or corrupted
- #2318 Problem with final qualifier in MultiPhase models
- #2349 Unused parameters in Modelica.Electrical.Analog.Semiconductors.SimpleTriac
- #2360 Missing test or example model for Modelica.Electrical.Analog.Semiconductors.HeatingPNP
- #2375 (PR) FixUnits
- #2402 Zener Diode Symbol incorrect
Enhancements
- #2186 Questionable constantVoltage Symbol
- #2201 Add MultiSensor to Analog, MultiPhase and QuasiStationary electrical packages
- #2215 Unify location of connectors in Electrical libraries
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2309 Add variable for representing torque/force in electromechanic converters
- #2399 Add adaptor components to Modelica.Electrical.Analog
- #2560 Change units of potential quantities in connectors to potential units
- #2563 (PR) Change units of potential variables of connectors (#2560)
- #2569 Default component name for adaptors
- #2570 (PR) Add default component name for adaptors (#2569)
- #2746 (PR) Add number of inductors to icon display of M_Transformer
- #2748 (PR) Refs #2735: Improve dots in icon of M_Transformer
Examples
- #576 Move
Rn
and Rp
models into the Utilities
package
- #2017 Modeling of Modelica.Electrical.Analog.Examples.OpAmps.SignalGenerator
- #2224 Missing parameter comments in Modelica.Electrical.Analog.Examples.OpAmps models
- #2268 Illegal modifiers in Modelica.Electrical.Analog.Examples.HeatingNPN_OrGate
- #2533 (PR) Fixes #576 by replacing internal models by one utility model
- #2608 Missing test or example model for Modelica.Electrical.Analog.Ideal.IdealOpAmpLimited
- #2644 (PR) Add example model for Modelica.Electrical.Analog.Ideal.IdealOpAmpLimited
Documentation
- #2222 Error in description of IdealizedOpAmpLimted
- #2223 Diode2: typo in description
- #2287 Update contributor's affiliations
Miscellaneous
- #1791 Comment string of M_Oline.segment references non-existent G_ref
- #2225 Missing closing parenthesis in Modelica.Electrical.Analog.Ideal.IdealizedOpAmpLimted.useSupply
- #2232 Unused (protected) variable maxexp in HeatingDiode and ZDiode
- #2293 Irregular colors used in QuasiStationary packages
- #2307 Final modifier inheritance in Electrical.Analog sources
- #2343 Internal variables of Modelica.Electrical.Analog.Semiconductors.HeatingNPN are public
- #2493 Modelica.Electrical.Analog.Ideal.AD_Converter internal error check fails w/ OpenModelica (v1.11.0 Win64)
- #2561 (PR) Added more options for homotopy-based initialization of limiters
- #2588 (PR) Improve wording of electrical and magnetic connector descriptions
- #2634 (PR) Use constant pi
Electrical.Digital
Bugs
- #2003 Use of undeclared variables in Dialog.enable, Modelica.Electrical
- #2072 Illegal use of delay() in Modelica.Electrical.Digital.Delay.TransportDelay
- #2084 Duplicated functions getMemory and address in Modelica.Electrical.Digital.Memories
- #2085 Wrong loadSelector.filter annotation in Modelica.Electrical.Digital.Memories.DLATRAM and DLATROM
- #2100 Missing obsolete annotation
Enhancements
- #2214 (PR) Simplify conditional assignments in Fluid/Dissipation.mo
Examples
- #2107 Invalid Line.fillPattern annotation in Modelica.Electrical.Digital.Examples.Utilities.Counter3
Documentation
- #2047 Electrical Digital Delay docs mention initout
- #2287 Update contributor's affiliations
- #2445 Inconsistent 'Contact' section of User's Guides of packages
Miscellaneous
- #2082 Missing comment for String parameter Modelica.Electrical.Digital.Memories.DLATRAM.fileName
- #2163 (PR) Fix icon for Electrical.Digital
- #2532 (PR) Extend obsolete classes from ObsoleteModel
Electrical.Machines
Bugs
- #1666 RealOutput in SM_PermanentMagnet, etc. show up in component icon layer
- #2031 Modelica.Electrical.Analog.Basic.Inductor, Transformer, etc. render poorly on non-white backgrounds
- #2181 Core Loss models are missing m modification in coreParameters declaration
- #2184 StrayLoad loss model in MSL.Electrical.Machines, speeds that cross zeros
- #2278 Unify simulation tolerances of electric machine models
- #2379 EddyCurrent using non-resistance resistance-function
Enhancements
- #2215 Unify location of connectors in Electrical libraries
- #2279 Unify communication intervals of electric machine models
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2311 Remove
import Modelica;
- #2381 Extend InductionMachineData by effectiveStatorTurns
- #2382 Improve Modelica.Blocks.Math.WrapAngle
- #2506 Add a simple model of a hall sensor
Examples
- #2276 Add more examples to FundamentalWave libraries
- #2342 Unit mismatch in machine examples
- #2388 Additional machines example
- #2555 (PR) Add missing
each
in SynchronousInductionMachines
- #2683 Remove redundant connect in DCPM_CurrentControlled
- #2685 (PR) Refs #2683: Remove redundant connection in example
Documentation
- #2219 Improve ReleaseNotes in UsersGuide
Miscellaneous
- #2307 Final modifier inheritance in Electrical.Analog sources
- #2532 (PR) Extend obsolete classes from ObsoleteModel
Electrical.MultiPhase
Bugs
- #2117 Electrical icons not homogeneous
- #2202 Remove redundant (and not identical) parameter m from mutual inductor models
- #2318 Problem with final qualifier in MultiPhase models
Enhancements
- #1997 SymmetricalComponents
- #2200 Symmetry condition of MutualInductor model is occasionally too tight
- #2201 Add MultiSensor to Analog, MultiPhase and QuasiStationary electrical packages
- #2215 Unify location of connectors in Electrical libraries
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2311 Remove
import Modelica;
- #2397 A better Multiphase power sensor
Documentation
- #2219 Improve ReleaseNotes in UsersGuide
Miscellaneous
- #2217 Wrong comment on Modelica.Electrical.MultiPhase.Sources.SignalCurrent
- #2362 (PR) Fix line color of Diode
- #2588 (PR) Improve wording of electrical and magnetic connector descriptions
- #2614 (PR) Fix spelling of description of electrical components
Electrical.PowerConverters
Bugs
- #2150 Modelica.Electrical.PowerConverters.ACDC.Filter uses undeclared useFilter parameter
- #2185 Unify location of PowerConverter connectors in diagram layer
- #2195 Frequency parameter of Signal2mPulse should not be hidden when filter is disabled
Enhancements
- #2198 Add calculation of AC and DC power to connector interfaces in PowerConverters
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2311 Remove
import Modelica;
- #2417 PowerConverters
- #2418 (PR) Add step up power converter model including example to Electrical.PowerConverters, see #2417
- #2536 Threephase PWM algorithm(s) for DC/AC PowerConverters
Examples
- #2410 PowerConvert templates with current sensors
Documentation
- #2219 Improve ReleaseNotes in UsersGuide
Miscellaneous
- #2196 Replace Modelica_Electrical_PowerConverters by Modelica.Electrical.PowerConverters
Electrical.QuasiStationary
Bugs
- #2153 Remove Text.textColor attribute of Modelica v3.3 in graphical annotations for MSL 3.2
- #2202 Remove redundant (and not identical) parameter m from mutual inductor models
- #2210 Inductor, Transformer, etc. render poorly on non-white backgrounds
- #2251 Modelica.Electrical.QuasiStationary.MultiPhase.Blocks.SingleToMultiPhase does not conjugate inputs
- #2280 Problem with potentialRoot in Modelica.Electrical.QuasiStationary.Machines.BasicMachines.Components.PartialCore
- #2318 Problem with final qualifier in MultiPhase models
Enhancements
- #2173 Add polar and power quantities in ideal quasi stationary transformer model
- #2199 Add MutualInductor model to Electrical.QuasiStationary.MultiPhase.Basic
- #2200 Symmetry condition of MutualInductor model is occasionally too tight
- #2201 Add MultiSensor to Analog, MultiPhase and QuasiStationary electrical packages
- #2215 Unify location of connectors in Electrical libraries
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2311 Remove
import Modelica;
- #2442 Add quasi static voltage and current source models with integrated frequency sweep
- #2451 Improve single-phase and polyphase impedance models
- #2453 Change parameter names of frequency sweep sources from fMin and fMax to fStart and fStop
- #2560 Change units of potential quantities in connectors to potential units
- #2563 (PR) Change units of potential variables of connectors (#2560)
Documentation
- #2219 Improve ReleaseNotes in UsersGuide
- #2314 Missing documentation of ReferenceSensor
Miscellaneous
- #2293 Irregular colors used in QuasiStationary packages
- #2307 Final modifier inheritance in Electrical.Analog sources
- #2354 (PR) Add missing
each
in Electrical/QuasiStationary/MultiPhase.mo
- #2588 (PR) Improve wording of electrical and magnetic connector descriptions
- #2614 (PR) Fix spelling of description of electrical components
Electrical.Spice3
Bugs
- #1864 Consistent use of term technologieparameters
- #2086 Line color of Sources.V_constant, Semiconductors.D_DIODE and Semiconductors.C_Capacitor icons (Modelica.Electrical.Spice3)
- #2088 Comment of Modelica.Electrical.Spice3.Internal.Rsemiconductor.ResistorModelLineParams and ResistorVariables
- #2100 Missing obsolete annotation
- #2375 (PR) FixUnits
- #2376 Modelica.Electrical.Spice3.Internal.Functions.energyGapDepTemp returns eV or V?
Enhancements
- #1425 Conditionally uninitialized local variable dbrgdb in Modelica.Electrical.Spice3.Internal.Mos2.drainCurRevised used
- #2509 Change symbol of Modelica.Electrical.Analog.Spice3.Sources.V_constant
Examples
- #1274 Incorrect documentation for certain example models in the Spice3 library
Documentation
- #2287 Update contributor's affiliations
- #2523 Misleading documentation in Spice3 package
- #2790 Missing parameters in Spice3.Sources.I_pwl and V_pwl
- #2791 (PR) Fix comment and documentation of Spice3.Sources.I_pwl and V_pwl (#2790)
Miscellaneous
- #1984 Comment in Spice3.mo
- #2288 (PR) Introduce correctly spelled types and declare existing ones as obsolete
- #2792 Spice3 Constant Current source has no arrow
- #2797 (PR) Improve and fix icons of Modelica.Electrical.Spice3.Sources according to the icon convention
Fluid
Bugs
- #1995 Incorrect homotopy in Modelica.Fluid.Machines.BaseClasses.PartialPump
- #2100 Missing obsolete annotation
- #2156 Unknown choices in Modelica/Fluid/Fittings.mo
- #2406 MassFractionsTwoPort - code bug
Enhancements
- #2214 (PR) Simplify conditional assignments in Fluid/Dissipation.mo
- #2364 (PR) Add missing C_default to PartialMedium
- #2557 (PR) Added assertion to catch singularities from flow source components
Examples
- #2000 Modelica.Fluid.Examples.DrumBoiler: incorrect unit on output p_S
- #2060 Modelica.Fluid.Examples.Tanks.TanksWithOverflow does not respect variable bounds
- #2063 Update start value in Modelica.Fluid.Examples.InverseParameterization
- #2197 (PR) Fix unit of Real output signal p_S
- #2243 Missing initial assignments in Modelica.Fluid.Examples.ControlledTankSystem.ControlledTanks
- #2355 (PR) Add
each
element of Xi array in Fluid.Examples.TraceSubstances.RoomCO2WithControls
- #2374 Modelica.Fluid.Examples.AST_BatchPlant: Medium model to water/ sodium chloride missing
- #2515 Modelica.Fluid.Examples.HeatingSystem generating warnings in Dymola
- #2530 (PR) Consistent simple guess-values for Modelica.Fluid.Examples.HeatingSystem
- #2539 (PR) Decrease height in Modelica.Fluid.Examples.Tanks.TanksWithOverflow
- #2591 (PR) Add start value for RadioButton
- #2606 (PR) Change state event into time event to avoid warning in Modelica.Fluid.Examples.AST_BatchPlant.BaseClasses.Controller
Documentation
- #2322 Reference to very old Dymola versions in MSL documentation: remove all tool specific documentation from MSL
- #2345 (PR) Remove outdated tool references for issue #2322
- #2445 Inconsistent 'Contact' section of User's Guides of packages
Miscellaneous
- #2359 (PR) Avoid default Real parameter evaluation
- #2420 (PR) Pull request for Issue #2406
- #2528 (PR) Avoid division by zero in default homotopy-code for Modelica.Fluid.Machines.BaseClasses.PartialPump
- #2532 (PR) Extend obsolete classes from ObsoleteModel
- #2558 Reverting flow should be reversing?
- #2564 (PR) Fix wording: reverting -> reversing
Fluid.Dissipation
Bugs
- #1981 Dissipation.HeatTransfer functions singular at zero flow
- #2005 Incorrect use of enumeration in Dialog.enable
- #2066 Wrong annotation in Fluid.Dissipation
- #2213 (PR) Remove protected element from record
Enhancements
- #2214 (PR) Simplify conditional assignments in Fluid/Dissipation.mo
- #2311 Remove
import Modelica;
- #2747 (PR) Utilize RecordsPackage icon for Modelica.Fluid.Dissipation.Utilities.Records
Documentation
- #2289 Update Fluid.Dissipation project acknowledgements
- #2336 (PR) Fixes #2289 by updating the time line of the ITEA project
- #2337 (PR) Fix the licensor as this is the MA not XRG
- #2338 (PR) Removes note about an old MSL dependency
Icons
Bugs
- #2100 Missing obsolete annotation
Enhancements
- #2115 Add Modelica.Icons.FunctionsPackage
- #2300 Add RecordsPackage
Miscellaneous
- #2532 (PR) Extend obsolete classes from ObsoleteModel
Magnetic.FluxTubes
Bugs
- #1871 Why start value for Modelica.Electrical.Analog.Interfaces.ConditionalHeatPort.heatPort.T?
- #2031 Modelica.Electrical.Analog.Basic.Inductor, Transformer, etc. render poorly on non-white backgrounds
- #2308 Connector descriptions are partly missing or corrupted
Enhancements
- #2263 (PR) UseTimeEventsInstead
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2327 Newly introduced transformer components of FluxTubes use entirely different variable naming
- #2448 Change term "magneto motive" to "magnetomotive"
- #2563 (PR) Change units of potential variables of connectors (#2560)
Examples
- #2179 Invisible connection line in Modelica.Magnetic.FluxTubes.Examples.MovingCoilActuator.Components.PermeanceActuator
- #2180 (PR) Update FluxTubes.mo to make connection line visible
Documentation
- #2445 Inconsistent 'Contact' section of User's Guides of packages
Miscellaneous
- #2155 Magnetic Hysteresis Records should extend from Modelica.Icons.Record
- #2254 Typo, Tickness, in doc strings
- #2395 Fixed initial condition on a derivative in PartialGenericHysteresis
- #2461 (PR) Fixes issue #2395
- #2588 (PR) Improve wording of electrical and magnetic connector descriptions
Magnetic.FundamentalWave
Bugs
- #1666 RealOutput in SM_PermanentMagnet, etc. show up in component icon layer
- #2031 Modelica.Electrical.Analog.Basic.Inductor, Transformer, etc. render poorly on non-white backgrounds
- #2100 Missing obsolete annotation
- #2275 Double instance groundR shall be removed
- #2278 Unify simulation tolerances of electric machine models
- #2328 Propagation of wrong operational temperature to resistances
- #2403 Fix propagation of excitation leakage factor
- #2416 Magnetic machine models: CoreParameters
Enhancements
- #2279 Unify communication intervals of electric machine models
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2311 Remove
import Modelica;
- #2448 Change term "magneto motive" to "magnetomotive"
- #2560 Change units of potential quantities in connectors to potential units
- #2563 (PR) Change units of potential variables of connectors (#2560)
Examples
- #2274 Missing
each
in instantiation of FundamentalWave machine examples
- #2276 Add more examples to FundamentalWave libraries
- #2277 Initial conditions of FundamentalWave machine examples are not identical
- #2342 Unit mismatch in machine examples
Documentation
- #2208 Modelica/Resources/Images/Magnetic/FundamentalWave/Components/permeance.png
- #2219 Improve ReleaseNotes in UsersGuide
Miscellaneous
- #2049 Incorrect doc strings in RotorSaliencyAirGap
- #2293 Irregular colors used in QuasiStationary packages
- #2588 (PR) Improve wording of electrical and magnetic connector descriptions
- #2733 (PR) Add missing
each
in Magnetic.FundamentalWave
Magnetic.QuasiStatic
Bugs
- #1666 RealOutput in SM_PermanentMagnet, etc. show up in component icon layer
- #2184 StrayLoad loss model in MSL.Electrical.Machines, speeds that cross zeros
- #2328 Propagation of wrong operational temperature to resistances
- #2403 Fix propagation of excitation leakage factor
- #2416 Magnetic machine models: CoreParameters
Enhancements
- #1515 New quasi-static flux tubes library to be integrated in MSL
- #2050 Add RotorDisplacementAngle to Modelica.Magnetic.QuasiStatic.FundamentalWave
- #2279 Unify communication intervals of electric machine models
- #2301 Use defaultComponentName to shorten instance names in Diagram layer
- #2311 Remove
import Modelica;
- #2382 Improve Modelica.Blocks.Math.WrapAngle
- #2448 Change term "magneto motive" to "magnetomotive"
- #2538 (PR) Proposal of Magnetic.QuasiStastic.FluxTubes to be included in MSL
- #2563 (PR) Change units of potential variables of connectors (#2560)
Examples
- #2276 Add more examples to FundamentalWave libraries
- #2342 Unit mismatch in machine examples
- #2356 (PR) Add
each fixed=true
in Magnetic.QuasiStatic.FundamentalWave.Examples.BasicMachines.SynchronousMachines.SMPM_Mains
- #2386 Wrong orientation of voltage source in inverter examples
Documentation
- #2219 Improve ReleaseNotes in UsersGuide
- #2579 (PR) Fix image and class links
Miscellaneous
- #2049 Incorrect doc strings in RotorSaliencyAirGap
- #2218 Update icon of Modelica.Magnetic.QuasiStatic.FundamentalWave.Utilities
- #2293 Irregular colors used in QuasiStationary packages
- #2588 (PR) Improve wording of electrical and magnetic connector descriptions
- #2678 (PR) Add missing
each
Math
Bugs
- #1774 dgeev and dgeev_eigenValues inconsistent
- #2078 Modelica.Math.Vectors.interpolate lacks derivative
- #2100 Missing obsolete annotation
- #2240 Matrices Riccati functions define array size in terms of non-input variable
- #2252 Modelica.Math.Random.Utilities.impureRandomInteger: Not an uniform distribution for imin=1
Enhancements
- #2264 (PR) specifySmoothness of interpolate function
- #2311 Remove
import Modelica;
- #2382 Improve Modelica.Blocks.Math.WrapAngle
- #2691 (PR) Fixing Modelica.Math.Matrices.Utilities.toUpperHessenberg
Examples
- #2393 (PR) Fix the result file name
Documentation
- #2068 Vector.interpolate doc should mention it is linear
- #2249 Invalid ftp link in Math/Nonlinear.mo
- #2436 Bug in documentation of Modelica.Math.Matrices.eigenValues
Miscellaneous
- #2260 (PR) ImpureRandomInteger-probabilities
- #2532 (PR) Extend obsolete classes from ObsoleteModel
Mechanics.MultiBody
Bugs
- #1944 Utilize Modelica.Constants in MultiBody.World
- #2004 Use of undeclared variables in Dialog.enable, Modelica.Mechanics.MultiBody
- #2096 Inconsistency in choice comments of Modelica.Mechanics.MultiBody
- #2100 Missing obsolete annotation
- #2182 Non-effective variable MultiBody.Forces.SpringDamperParallel.specularCoefficient
- #2230 Animation of Modelica.Mechanics.MultiBody.Forces.LineForceWithTwoMasses
- #2375 (PR) FixUnits
- #2465 Modelica.Mechanics.MultiBody.Joints.Prismatic - s_offset - constant vs parameter
Enhancements
- #386 Animation missing in MultiBody.Forces.SpringDamperSeries
- #1843 Make Modelica.Mechanics.MultiBody.Visualizers.Ground usable for x- and y direction
- #2091 Utilize outerProduct in functions of Modelica.Mechanics.MultiBody.Frames
- #2171 Line force length assertion in Mechanics.MultiBody.Forces
- #2183 (PR) Add animation for SpringDamperSeries and SpringDamperParallel
- #2231 Add results to Modelica.Mechanics.MultiBody.Forces.Spring
- #2311 Remove
import Modelica;
- #2424 (PR) Added a 'Plane' visualizer based on Surface model
- #2432 Use ground plane visualizer directly in the World
- #2715 (PR) Fix icon text extent MultiBody
Examples
- #1810 State select in Modelica.Mechanics.MultiBody.Examples.Constraints models
- #1999 Connection to disabled frame_resolve
- #2039 Add planar four bar loop to MultiBody examples
- #2055 Underdetermined initialization of PointGravityWithPointMasses2
- #2317 Non-existent class referenced in choices annotation in Modelica.Mechanics.MultiBody.Examples.Loops.Utilities.EngineV6_analytic
- #2421 (PR) Mechanics.MultiBody: Improved Diagram layout of examples to better fit the grid
- #2439 Two similar GasForce models for MultiBody loops examples
- #2529 (PR) Remove incorrect stateSelect in constraint examples
- #2663 Stop time of Modelica.Mechanics.MultiBody.Examples.Systems.RobotR3.fullRobot
- #2664 (PR) Improve documentation of fullRobot example
- #2714 (PR) Fix connect text extent
Documentation
- #285 Improve/fix documentation of Modelica.Mechanics.MultiBody
- #2227 Incorrect argument order in Modelica.Mechanics.MultiBody.Frames.resolveRelative document
- #2228 (PR) Fix argument order in Modelica.Mechanics.MultiBody.Frames.resolveRelative document
- #2322 Reference to very old Dymola versions in MSL documentation: remove all tool specific documentation from MSL
- #2323 Modelica.Mechanics.MultiBody.UsersGuide.Tutorial.LoopStructures.Introduction is out-of-date
- #2335 (PR) Ref #2242: Remove misleading promise of future components
- #2445 Inconsistent 'Contact' section of User's Guides of packages
- #2503 Documentation for Frames.absoluteRotation references Frames.relativeRotation
- #2545 Missing DoublePendulumInitTip in package documentation
- #2777 (PR) Fix documentation of MultiBody.Frames functions
Miscellaneous
- #2090 Calling Modelica.Math functions in functions of Modelica.Mechanics.MultiBody.Frames
- #2194 Duplicated convertElement (with same arguments) in conversion scripts
- #2366 (PR) Remove duplicated convertElement commands
- #2368 (PR) Remove choices annotation for Cylinder model
- #2405 Remove comparison signal from regression test
- #2426 Redundancy in Modelica.Mechanics.MultiBody.Sensors.Internal
- #2433 (PR) Remove the superfluous "for menus" in comments
- #2651 (PR) Remove ineffective Evaluate annotation from inputs in FixedShape / FixedShape2
Mechanics.Rotational
Bugs
- #2100 Missing obsolete annotation
Enhancements
- #1993 Eddy Current Brake
- #2423 Add parameter "radius" to icon of IdealRollingWheel
- #2466 Question on behavior of OneWayClutch
- #2469 Remove superfluous representation of 'ground' in icons of Torque and Force
- #2480 Improve icons of sources
- #2622 (PR) Add default component name to old rotational adaptors
Examples
- #1975 Not quite 90 degrees, in Modelica.Mechanics.Rotational.Examples.CoupledClutches
Documentation
- #2298 Fix documentation string of Rotational.Interfaces.Flange_a and Flange_b
- #2445 Inconsistent 'Contact' section of User's Guides of packages
- #2467 Documentation error in OneWayClutch
Miscellaneous
- #2371 Missing inheritance in Mechanics.Rotational.Components.Inertia
- #2430 Obsolete adaptors in Mechanics.Rotational.Component
- #2520 (PR) Using green toned colors in Mechanics.Translational
- #2585 (PR) Fix rotational adaptor icons
- #2696 Icon of models with states
- #2710 (PR) RelativeStates icon
Mechanics.Rotational3D
Examples
- #1999 Connection to disabled frame_resolve
Mechanics.Translational
Bugs
- #2059 Incorrect variables in description of stateSelect parameter in translational components
- #2100 Missing obsolete annotation
Enhancements
- #2269 Add adaptor components to Mechanics.Translational
- #2311 Remove
import Modelica;
- #2423 Add parameter "radius" to icon of IdealRollingWheel
- #2469 Remove superfluous representation of 'ground' in icons of Torque and Force
- #2480 Improve icons of sources
- #2569 Default component name for adaptors
- #2570 (PR) Add default component name for adaptors (#2569)
Documentation
- #2445 Inconsistent 'Contact' section of User's Guides of packages
- #2487 Copy/paste error in documentation of Mechanics.Translational.Interfaces.Support
Miscellaneous
- #2486 Use dark green color in icons of Modelica.Mechanics.Translational
- #2520 (PR) Using green toned colors in Mechanics.Translational
- #2696 Icon of models with states
- #2710 (PR) RelativeStates icon
Bugs
- #1922 Wrong coefficients in some ideal gases (CH2, CH3, CH3OOH, C2CL2, C2CL4, C2CL6, C2HCL, C2HCL3, CH2CO_ketene, O_CH_2O, HO_CO_2OH, CH2BrminusCOOH, C2H3CL, CH2CLminusCOOH, HO2, HO2minus, OD, ODminus)
- #2236 Modelica.Media.Examples.MoistAir violates min/max attributes
- #2377 What is the unit of R?
- #2378 (PR) InvertMolar
- #2385 Incorrect assert statement in IF97_Utilities.BaseIF97
- #2437 (PR) Bug fix for ticket #2377
- #2719 Bug in the modified Eucken method of Modelica.Media.IdealGases.Common.Functions.thermalConductivityEstimate
- #2734 (PR) Issue #2719 modified Eucken R in J/kg.K
- #2764 Unit conversion bug in Media.IdealGases.Common.MixtureGasNasa.mixtureViscosityChung
- #2778 (PR) Fix conversion from microPoise to Pa.s in mixtureViscosityChung
Enhancements
- #2121 C_default not defined in Modelica.Media.Interfaces.PartialMedium
- #2263 (PR) UseTimeEventsInstead
- #2286 PartialTwoPhaseMedium FluidConstants should be replaceable
Examples
- #2352 (PR) Add missing
each
in Modelica.Media.Examples.TestOnly.MixIdealGasAir
- #2522 (PR) Add missing StopTime annotations to examples
- #2542 (PR) Cleanup Media test models (#1053)
- #2543 Clarify description of Modelica.Media.Examples
- #2744 (PR) Fix example description
- #2755 (PR) Fixes #2543 by removing the misleading promise
Documentation
- #2294 Outdated Media Future
- #2322 Reference to very old Dymola versions in MSL documentation: remove all tool specific documentation from MSL
- #2345 (PR) Remove outdated tool references for issue #2322
- #2445 Inconsistent 'Contact' section of User's Guides of packages
Miscellaneous
- #2238 (PR) Resolved issue #2236 for high saturation pressures and temperatures
- #2296 (PR) make FluidConstants in PartialTwoPhaseMedium replaceable
- #2331 (PR) Remove "Future" chapter because it was outdated
- #2490 Typo over0stochiometric
- #2499 Wrong description for triple.ptriple
- #2532 (PR) Extend obsolete classes from ObsoleteModel
- #2559 (PR) Removed commented reference to non-existing medium
- #2617 (PR) Add missing
each
in Media.Air.MoistAir.s_pTX_der
- #2648 (PR) Remove ineffective Evaluate annotation from constants in PartialMedium
- #2678 (PR) Add missing
each
ModelicaReference
Bugs
- #2324 ModelicaReference.Operators.'sign()' does not generate events
Documentation
- #2128 What is the usage recommendation for class?
- #2129 Update documentation of ModelicaReference.Classes.ExternalObject
- #2384 (PR) Improve wording
- #2505 (PR) update versionBuild and point to semver as alternative for usage in ModelicaReference
- #2577 (PR) Fixes closing HTML tag and table attribute
- #2689 checkbox versus checkBox
- #2690 (PR) Fixes #2689 by correcting the spelling of the "checkBox" annotation
- #2721 ModelicaReference.Annotations.Documentation contains unresolvable URIs
- #2723 (PR) Fixes #2721 by using a more abstract package as example
- #2798 Incomplete class table for extends in ModelicaReference
- #2799 (PR) Fixes #2798 by updating the table.
- #2800 (PR) Ref #2787 since CLA is signed, no need to have copyright of Dietmar Winkler
Miscellaneous
- #2325 (PR) Several minor updates of Modelica Reference
- #2380 (PR) ClarifyBreakable in ModelicaReference
ModelicaServices
Documentation
- #2133 Fix the license info for the ModelicaServices library on the MA server
Miscellaneous
- #2211 Tool-neutral Modelica.Utilities.System.exit
- #2504 (PR) Fixes #1822 by removing the Protection annotation and bump version
ModelicaTest
Bugs
- #1900 Clean up of sensitive test for Modelica.Fluid
- #1963 Discontinuous change in angles/positions of PlanarLoopWithMove
- #2081 Math.Random functions special and distributions only succeed for default arguments
Enhancements
- #2266 (PR) UseTimeEventsInsteadInModelicaTest
- #2311 Remove
import Modelica;
Examples
- #2542 (PR) Cleanup Media test models (#1053)
- #2772 (PR) Add test model for Modelica.Utilities.Examples.calculator
Miscellaneous
- #1604 Identifier typo in ModelicaTest.MultiBody.Parts.Rotor1D.Beveal1d
- #2149 Naming of ModelicaTest.MultiBody.Forces.Worldtorque
- #2392 (PR) Added call of file() to ModelicaTest, resolves #2391
- #2407 CombiTable2D tests with unknown variables in reference results
- #2561 (PR) Added more options for homotopy-based initialization of limiters
- #2705 Initialization of ModelicaTest.MultiBody.Joints.SphericalSpherical2
- #2730 (PR) Set guess values of ModelicaTest.MultiBody.Joints.SphericalSpherical2
- #2773 (PR) Add test model for Modelica.Math.Matrices.Examples.solveLinearEquations
- #2784 Analysis of ModelicaTest v3.2.3-rc.1+71590c7 regressions vs. v3.2.2+build.0-beta.3
- #2810 Analysis of ModelicaTest v3.2.3-rc.2 regressions vs. v3.2.2+build.0-beta.3
Resources
Enhancements
- #2527 (PR) Improve granularity of Release Notes
- #2547 (PR) Rename _readme.txt to readme.txt
Documentation
- #2507 (PR) Replace outdated Documentation and ReleaseNotes Templates with generation script and template
SIunits
Bugs
- #2100 Missing obsolete annotation
- #2284 First (and Second) Order Temperature Coefficient types misspelled in Modelica.SIunits
Enhancements
- #1911 Add new type
Modelica.SIunits.ComplexPerUnit
- #2131 Ugly icon for Modelica.SIunits
- #2444 (PR) Added documentation strings to real and imaginary parts of complex units
Documentation
- #2445 Inconsistent 'Contact' section of User's Guides of packages
Miscellaneous
- #2288 (PR) Introduce correctly spelled types and declare existing ones as obsolete
StateGraph
Enhancements
- #2263 (PR) UseTimeEventsInstead
Documentation
- #2297 (PR) Update documentation of StateGraph.Temporary.SetRealParameter
- #2445 Inconsistent 'Contact' section of User's Guides of packages
- #2739 (PR) Fix outdated links
Miscellaneous
- #2740 (PR) Declare temporary StateGraph classes as obsolete
Thermal.FluidHeatFlow
Bugs
- #2549 FluidHeatFlow.Sources.IdealPump: equations have a flaw
- #2571 (PR) FluidHeatFlowDesignFlaw
- #2701 (PR) Fix equation of pressure increase versus volume flow in IdealPump
Enhancements
- #2550 Size of signal input connectors in FluidHeatFlow
- #2551 FluidHeatFlow: model of an open tank
- #2552 Add annotation(defaultComponentPrefixes) to FluidHeatFlow Media records
- #2553 FluidHeatFlow - add a cylinder model
- #2582 (PR) FluidHeatFlowEnhancements
Miscellaneous
- #2148 Simplify Initialization of Modelica.Thermal.FluidHeatFlow.Interfaces.Partials.TwoPort
- #2154 (PR) close #2148
Thermal.HeatTransfer
Enhancements
- #2400 Add adaptor components to Modelica.Thermal.HeatTransfer
- #2569 Default component name for adaptors
- #2570 (PR) Add default component name for adaptors (#2569)
UsersGuide
Documentation
- #2165 Reflect transition from Subversion to Git in UsersGuide
- #2287 Update contributor's affiliations
- #2427 (PR) Fix incorrect case
- #2447 (PR) Included documentation package on terms and spelling
- #2457 (PR) Suggestion for a new template for libraries' contact information
- #2498 OMC links in Release Notes
- #2510 Dead project link
- #2511 (PR) Update version management
- #2516 (PR) Remove usage of SVN revisions in conventions
- #2518 Broken URI to image in User's Guide
- #2565 Release notes 3.2.3
- #2566 (PR) Finalize the Release Notes 3.2.3
- #2586 (PR) Fix typos
- #2707 (PR) Fix closing parenthesis
Utilities
Enhancements
- #2365 (PR) Add asin(), acos(), atan(), exp(), log() to the calculator grammar
Examples
- #1869 Enhancement of Modelica.Utilities.Examples.expression
- #1990 Modelica.Utilities.Examples.ReadRealMatrixFromFile issue
- #2464 (PR) Fix location and link to Examples_readRealParameters.txt
Documentation
- #2099 Fix documentation of Modelica.Utilities.Streams.error
- #2141 New function Modelica.Utilities.Strings.hashString is not listed in the package documentation table
- #2292 Document race condition in tmpnam, called by ModelicaInternal_temporaryFileName
- #2367 (PR) Fix the documentation of Modelica.Utilities.Streams.error
- #2445 Inconsistent 'Contact' section of User's Guides of packages
- #2462 (PR) Add missing function loadResource to table of functions
- #2463 (PR) Fix name of loadResource in doc
Miscellaneous
- #2144 Improve comment on Modelica.Utilities.System.getEnvironmentVariable.convertToSlash
- #2211 Tool-neutral Modelica.Utilities.System.exit
- #2391 Missing test or example model for Modelica.Utilities.Files.list


{% include "header.html" %}
{% block title %}Marketplace{% endblock %}
Welcome to the Marketplace
Services
Appliances
Storage
Compute
NAME
DESCRIPTION
PROVIDER
{% for items in market %} {% if items.tag == "service"%}
{% elif items.tag == "appliance"%}
{% elif items.tag == "compute"%}
{% elif items.tag == "storage"%}
{% endif %}
{{items.name}}
{{items.desc}}
{% endfor %}
×
Close
Title of Service
Compute
Small
Medium
Large
Storage
BU-small
EMC-large
Network
Public


On Korea: A Brief Summary of My Experience
After 24 hours inside airplanes, more than 10 hours waiting on airports, 2 connections, and 2 more hours in a bus, I finally arrive at the hotel. To enter the building, I pass through the outward doors with my hefty luggage, but, as I go through the second, an ill-calibrated timer closes it on me, making me stuck at the entrance of the main hall: while a paralyzed hostess watches the scene struggling to come up with a solution, I have a strange premonition that this whole situation will be a metaphor of my incoming stay in the country.
For those who don’t know my background — for those who do, please bear with me this n-th repetition of the same story —, throughout university, during my bachelors degree in engineering, I saw my interest in the field wane: the jumbled world of abstractions presented by the professors seemed only to needlessly complicate a world that was much simpler in the daily practice. As a result, I couldn’t help but erroneously generalize the feeling of emptiness to life itself.
I could even argue that this hole, the death or coma of interest, was the main reason why I decided to take part in an exchange program in Europe one year and a half earlier. Consciously, I deeply wanted my love for science to rekindle during my stay in the old continent, however, subconsciously, my general interest for life was at stake.
That somewhat brief one year period revolutionized my life. Unexpectedly, Go — Baduk or Weiqi —, a hobby I learned in my second year at university, brought me a family which taught me the real value of friendship, a new language — French — and a lifelong set of lessons I’m still learning from.
Coming back to my last semester in my original university I soon
realized the diagnosis of my lack of interest was worse than before
with respect to my courses. Only Go would shine in my mind
Obviously worried about my future, I didn’t want to land on the other
side of the globe without a plan. The first choice that comes to mind
is to go for the intense monk-like training inseis tend to have.
However, this did not seem to be a good prospect, as I would most
likely not become as strong
At the time all this internal storm was raging, my interest for the exact sciences was, as previously mentioned, essentially dead. With the puzzling effect of my experience in Europe, I couldn’t help but gradually dive into the mysteries of social interactions. Eventually, the question I was internally urged to solve became more clear: with respect to Go — and, more generally, board games — what would be the set of good behaviors and attitudes which would most likely yield a good social interaction? Hopefully, answering that enigma would make me and many others able to better control the environment of a Go Club, letting the game be more enjoyable and the related emotions less of an issue.
That question is mostly a subject of the not so well known — much to the shame of academics — field of microsociology, the middle child of the sociology and psychology brothers. This field studies interactions within groups of individuals and is sometimes considered a black sheep due to the fact that you can’t use reliable statistics like you do in sociology — since the population is too small — and neither can you blindly generalize the extensive body of work psychology has created for the behavior of individuals. Nevertheless, there are some important concepts which have been safely confirmed; and, probably, the most relevant to the aforementioned question is the Shame Loop.
The Shame Loop has been a recurrent topic for psychologists
and nothing really new, however it does not only have an effect on the
individual but, also, on the interaction. In simple terms, whenever
someone becomes a victim of shame, he or she tends to lower
self-esteem, to the point of causing more shame and, thus, creating a
destructive spiral. But, in a less expected manner, this spiral also
acts on the interaction between individuals, because it is observed
that when one of the actors demonstrates that he or she is ashamed,
the other person will most likely also feel ashamed for making the
other ashamed, and so on, shaping another spiral. This phenomenon can
be seen in various social occasions, and I would argue that it’s very
frequent in Go: rarely will you see players who take losing healthily;
and no wonder the more emotionally stable players are usually the
stronger ones
The basic advice psychologists would give you to dispell the
Shame Loop is to be conscious about the phenomenon —
acknowledging it helps it to not be transformed into general anger or
indifference — and to be surrounded by loving people who can
help you overcome it. But Thomas J. Scheff, in his
chef-d’œuvre
Microsociology
After settling for the mix of academic research and Go training, I spent some time trying to find a suitable institution which would help me achieve my goals. It was mostly difficult to find any, since my requisites were very specific and the language barrier was enormous – I only had some rudiments of Chinese. Eventually, I converged to basically the only institution that had a seemingly reasonable fit: Myongji University, more specifically the Department of Baduk Studies. This school was founded by Professor Jeong Suhyeon (정 수혀), a psychologist and Korean 9p, credentials which, at least at a superficial level, helped assure me the department had some rigor.
However, once in South Korea — and also before arriving there —, I started to realize that some things were off.
The most flagrant one was the fact that there were very few Westerners in the Department. Despite so many ardent Go lovers in the West, only a handful of them were there and none in my year — I had only one colleague in my year of the Master’s program, a young Chinese economist. Although the Department incentivized — mostly with full scholarships — foreigners to come and study there, after 20 years of existence, most of them wouldn’t take the offer. And the reason comes from two factors.
Firstly, the school was created to satiate a need: as Go grew in popularity in South Korea, more and more people would like to take it as profession, but, having no credentials and no other skills besides playing, a lot of people would end up unemployed, and a lot of professionals, with insufficient income. The Department of Baduk Studies gave these individuals sufficient technical means for teaching Go and credentials which would enable them to be valued by society, surely an accomplishment worthy of praise. This whole environment, however, was never intended to those who sought different goals and, thus, Westerners would invariably be disappointed.
In second place as an issue, I would rank the academic deficit. I do not recall, in my one semester stay, having heard of any paper or research that came out of this Department as being relevant to any other fields, though, again, 20 years have gone by. And it is not as if their field were anything new, it is just an application of much wider areas of knowledge, such as psychology, history and game theory. In my opinion, this school lacks a strong academic leadership, which could be achieved through catering Go loving researchers, who are, in fact, sufficiently numerous for that purpose.
Another problem that deeply disappointed me is the inexistence of a
systematic method of improving the strength of the students. Due to
many, if not most, of the students already being professionals or very
high ranked amateurs, I believe the professors saw no gain in having
some kind of league or training to improve the students’ strength;
but, to the international ones, it feels like staying for years in the
Shaolin Temple and being able to, at best, only watch the monks train.
Of course, the underlying work to manage such a system would be too
much for the professors alone, but they could, for example, much like
in monasteries, make it mandatory for stronger students to help weaker
ones or just outright hire Go teachers: after all, having a Department
of Baduk Studies which does not directly include studying the game
feels wrong at a core level
Overall, my critique of the school is negative, but I must stress the fact that the people I met there were very kind and welcoming. The professors, for instance, mostly helped me whenever possible and even tried to convince me to stay when I decided to quit the Master’s degree.  If you wish to know more about it, feel free to message me through Facebook or get in touch with Prof. Daniela Trinks, who is the main point of contact for Westerners in the Department.
By far this was my biggest underestimation in years. From gleaning
through Korean textbooks, after learning the alphabet, you will
probably have the impression that this is an easy language, or, at the
very least, the easiest among the Asian ones. Wrong
What King Sejong (세종), the historical father of modern Korean, did was, at its surface, marvellous, a beautiful simplification. Nonetheless, the Chinese background still remains, which makes things very unexpectedly confusing to learn. King Sejong replaced the Chinese ideograms for an alphabet, which makes writing much simpler, since you don’t need to memorize thousands of symbols anymore, however, this also brings a lot of other sources of mistakes, because, now, all the inherent Chinese homophones have also become homographs, thus having essentially no way of differentiating themselves. In other words, you will end up with a lot of words that, for different contexts, will have completely different meanings — this also greatly diminishes the value of dictionaries, since definitions cannot be very concise anymore. Homographs and homophones are normal for basically every language, but the sheer scale they take in Korean is just appalling, frightening, for any beginner, who will be second guessing every phrase he or she hears or, even, reads.
However, when I mention my massive underestimation, I’m actually referring to my approach of learning the language. My plan was to learn it on the go and only when I needed to, after all, my main interests were Go and psychology, not Korean. This is very unlike my general attitude towards languages, which is generally of considerable interest; but, in the case of Korean, I couldn’t help but feel hopeless once I realized that the vast majority of the resources I could use as a beginner came from pop culture, an area mostly lacking in content quality. As a result, the more I tried to learn Korean, the more I wished I had stuck to Chinese instead, with their bigger, longer, stronger cultural heritage.
In sum, it is clear that learning Korean — or any language, really — the way I tried to is a recipe of failure. Instead, it would have been much more effective to follow the path many Westerners and some other Asian foreigners took — and that only much later I discovered I was eligible to —: take a semester or a year of sole dedication to the language, in a program most South Korean Universities offer, with steep discounts for their graduate students. I don’t know if I would have gone to South Korea if such a program were mandatory, but it was at least a worthwhile consideration.
It is true that I haven’t traveled that much in South Korea —
nor have I spent that much time there —, so this won’t be an as
comprehensive a guide as I would like it to be. Nevertheless, I’ve had
enough experience in some of the more important environments, that is,
those most people will likely spend the majority of their time
in
Korea has become the embodiment of all of the capitalist principles, a
country that works: which does not necessarily mean
fulfillment
One curious side effect of it is related to the book shop density in the big cities. I was very surprised to almost not find a book shop in the medium sized town I was living in — Yongin (용인) —, and how sparse book shops in Seoul (서울) are — you may have to Google for them in order to find one. In comparison with Western large developed cities, where you can find a book store within some blocks or, at least, in every shopping mall, I was a bit baffled by Korea. Besides the internet, the only explanation I could arrive at is that their education, though high in many standards, is mostly utilitarian and competitively oppressive, a perspective which does not usually incentivizes the reader to keep on learning.
n the end, the final form of capitalism seems to be a Korean marketplace — with many offices on top —, where people both work and buy, all in one place, and where people can also have a break from their tiresome schedules by playing bowling with their work colleagues or having overnight Starcraft sessions, or, perhaps when feeling too much stress, release their anger violently, inside a bat cage.
Obviously, this is just my opinion, which I mostly focused on the aspects that affect the majority of the population, and which I found most memorable and wicked. Though South Korea has a lot of facets I believe are just flat out wrong or bad for human existence, I must make a concession to state that their people are overall some of most compassionate I’ve ever met. Despite the occasional feeling of being a zoo attraction of the Western subspecies, spending time with them is mostly very pleasant.
After my final decision of quitting Myongji was made, I still had
about 45 days before my flight back home. Although I could move it
forward I chose to stay and try out a more intense training
experience. Since I already had some friendship with the people at
BIBA
My initial idea was to stay more than 45 days if I liked the
experience, however, eventually, money also took its toll in
convincing me to go back at the previously scheduled date. BIBA has
its pros and cons
I’ve learned a lot from the teachers there, specially when it comes to
training — Diana’s unbelievable persistence at teaching me how
to solve tsumegos… — and another much more pragmatic approach to
Go. The last days in the school were tough on my completely exhausted
self, I had doubts all over the place about my future and felt an
utmost disappointment at how big a failure this attempt of a new life
based on Go on the other side of the planet was, but, at least, BIBA
gave me a sensation of closure, a more open mind, and taught me the
value of repetition — not to mention the necessary wisdom to
arrive at the meaning of life
For a long time I’ve been trying to learn from my stay in South Korea — about one year now —, and I’ve come up with a miscellanea of explanations for why it didn’t work out and why I eventually decided to quit. In a concise summary: it wasn’t worth it — which is a totally subjective statement.
During my stay, I saw students, friends and professionals put an ungodly amount of work into Go only to be recognized as marginally valuable by others and, in doing so, they would invariably have to let go of other pursuits for knowledge, either due to a lack of time or a lack of energy, something my personality absolutely cannot stand, as I view specialization as a consequence and not a primary objective — which is a bad perspective for life nowadays, since capitalism basically only values specialized intellect.
In parallel, I saw myself fully committed in a Master’s program I found more and more questionable both in terms of helping me achieve my desired goals as a researcher and in terms of financial prospects, while having to bash my head against the Korean language everyday and face the naturally subtle ostracization of Korean society. Ultimately, my passion for Go did not cut it — in fact, it remains in a coma to this day, mainly only creating online educational content for beginners.
At the very end, in one of my last days, as I ate with the other BIBA students while being filmed by a TV crew of a documentary on international Go players in South Korea, I became paralyzed by fear and sadness, remembering the infinite set of doors I had got stuck in, when they asked: what will you miss about Korea?


[§356D-29] Quitclaim deeds. Unless otherwise provided by law, the authority shall issue quitclaim deeds and leases whenever it conveys, transfers, sells, or assigns any property developed, constructed, or sponsored under this chapter. [L 2006, c 180, pt of §2]