The top layer is a piece of pyroceramic glass. It can withstand huge temperatures and supports very well abrupt temperature changes. This also means that it doesn't change shape at all when heated. This is the most critical requirement of a high end build platform for a 3D printer. If the base isn't perfectly flat (I mean down to 0.05mm precision)the prints will come out wrong.
The Dev Donkey Blog
something something software
Thursday, April 25, 2013
Custom Heated Build Platform for Prusa Mendel 3D Printer
A lot of things going on at Pentaho have kept me away from this blog in the past months, but in the meanwhile, in my spare time, I've been playing with a couple of things. I had time to pimp up my 3D printer's heatbed for one thing.
Tuesday, September 18, 2012
Programmatic roles in Mondrian
I often get asked how to use custom programmatic roles in Mondrian. It is actually very simple to get started. All you need is Mondrian and its dependencies, along with the following code.
It happens in three parts.
First you need to create a MondrianServer instance.
The second argument is used to translate the catalog URLs provided by the RepositoryContentFinder into actual paths on a file system or HTTP or whatever is required. This allows to decouple the contents of the XML, which can be shared by multiple Mondrian server instances, from the physical paths on actual machines. Notice that behind the scenes, Mondrian uses Apache VFS, so anything is possible here.
It happens in three parts.
First you need to create a MondrianServer instance.
MondrianServer server =The first argument must implement RepositoryContentFinder and provides a "piece of XML" to the Mondrian server. This tells it which datasources, catalogs and schemas to use. You can either take a look at some examples or refer directly to our DTD.
MondrianServer.createWithRepository(
new DynamicContentFinder("path/to/datasources.xml"),
new IdentityCatalogLocator());
The second argument is used to translate the catalog URLs provided by the RepositoryContentFinder into actual paths on a file system or HTTP or whatever is required. This allows to decouple the contents of the XML, which can be shared by multiple Mondrian server instances, from the physical paths on actual machines. Notice that behind the scenes, Mondrian uses Apache VFS, so anything is possible here.
Entry roleToken =This next part registers the Role implementation to use. You can either override our default implementation, or implement the API directly. Registering an object with a server gives you a token back. You will have to use this token when you create your olap4j connection, like so,
server.getLockBox().register(
new RoleImpl() {
// Override whatever here.
// You could also implement Role directly.
});
OlapConnection connection =And voilĂ .
server.getConnection(
"Catalog Name",
"Schema Name",
roleToken.getMoniker(),
new Properties());
Saturday, May 12, 2012
A Machine That Goes Bing!
Some of you might remember the famous sketch from Monthy Python's The Meaning of Life featuring the machine that goes Bing!
Although its sole purpose is to go Bing!, the concept of such a machine appealed to me for no particular reason. Besides, I had a few electronic parts that I needed to test so I figured that a machine that goes Bing! was just as good as any.
Although its sole purpose is to go Bing!, the concept of such a machine appealed to me for no particular reason. Besides, I had a few electronic parts that I needed to test so I figured that a machine that goes Bing! was just as good as any.
Tuesday, April 3, 2012
Oracle Essbase Sample.Basic on olap4j & Saiku Analytics
The olap4j project has had a regain in momentum lately, when community contributor Mark Semsel joined the project and offered to do some work on making olap4j compatible with Oracle Essbase. This is a very interesting milestone. We can scratch one more backend vendor from our to-do list.Who knows what's next.. too soon to whisper SAS?
Stay tuned!
Stay tuned!
Thursday, March 15, 2012
Unified DIFF from perforce changelist spec
Because this snippet is very useful when dealing with Perforce, I thought I'd share it real quick.
Ever wondered how to obtains a DIFF of a specific changelist spec? Try this.
($1 is the P4CLIENT name and $2 is the changeset spec)
Ever wondered how to obtains a DIFF of a specific changelist spec? Try this.
($1 is the P4CLIENT name and $2 is the changeset spec)
P4CLIENT=$1 p4 opened -c $2 | sed -e 's/#.*$//' | P4CLIENT=$1 p4 -x - diff
Subscribe to:
Posts (Atom)