Slashdot Mirror


KDE Conquers Astrophysics With Kst

Telex4 writes "The Free Software community is constantly inundated with interesting new projects, but occasionally something crops up which is really special. Kst is just such a project. Started by Barth Netterfield, an astrophysicist, as a personal project to plot data from his experiments, it has now taken on a life of its own, being used in numerous academic projects, and finding funding from several government agencies. Intrigued by this project's success, and with a little prod from co-developer George Staikos, I interviewed Barth and George about kst, Free Software and physics."

49 of 195 comments (clear)

  1. KDE Naming by Anonymous Coward · · Score: 5, Funny

    I suppose its slightly better than KastroPhysics.

    1. Re:KDE Naming by Anonymous Coward · · Score: 3, Funny

      Shouldn't the headline read "KDE Konquers Kastrophysicists kith Kst"?

    2. Re:KDE Naming by name773 · · Score: 3, Funny
      communism = beards * cigars^2
      you forgot vodka. the following equation will compensate:

      communism = (beards * (cigars + vodka)^(1 + 1/e))

  2. Pychart by updog · · Score: 5, Informative
    That definitely looks cool - another nice way I've found to plot data in a Python/QT environment is with Pychart

    It's easy to generate png/pdf/ps plots and they look really nice.

    1. Re:Pychart by bloosqr · · Score: 4, Informative

      If you like Python for doing plotting check out vpython Its basically a very simple opengl interface glued into python. Its actually originally designed to as a "computational physics" pedagogy language (which its really pretty fantastic for actually) but since its really just python its very easy to turn it into a poor mans 3d/4d plotting program :)

    2. Re:Pychart by Satai · · Score: 4, Informative

      Hell, why stop there? VTK and MayaVi are also pretty amazing visualization kits, both of which are either written in or provide python bindings. (MayaVi is built on VTK, but it provides a nice wrapper.) VTK has great isosurface locaters and some pretty awesome vector algorithms for looking at 2d and 3d data. We use it for physical applications at my work...

  3. "kst"? by kst · · Score: 4, Funny

    For the record, I had nothing to do with this.

  4. Shouldn't that be "Konquered"? by Anonymous Coward · · Score: 3, Funny

    As in "konquered astrophysiks"? How else can I tell that it was written for KDE?

  5. Lets not let this go to our heads by Anonymous Coward · · Score: 4, Interesting

    The author used Linux/KDE because that is what he was familiar with when he developed it. Its not suprising since universities are very UNIX centric. But that doesn't necessarily mean KDE is better suited for this type of application. In my opinion, no operating system/window manager will really have any significant advantages since the bulk of the work is number crunching. It could of easily been done in Win32.

    1. Re:Lets not let this go to our heads by Jeremy+Erwin · · Score: 4, Interesting

      Unix systems have had a historical advantage in scientific computation. Netterfield mentioned that he had first used XForms, looked at gtk+, felt queasy and decided to use KDE instead.
      As Kst is primarily a plotter of data, his choice of graphics toolkit is of some importance.

  6. I'm sure many will ask this... by ZuperDee · · Score: 4, Interesting

    Why didn't the article headline read, "KDE Konquers Astrophysicists with Kst?"

    On a more serious note: This question wouldn't arise if KDE people didn't insist on prefixing EVERYTHING with "K." Of course, same goes for GNOME folks prefixing everything with "G." Why is this necessary?

    1. Re:I'm sure many will ask this... by ErichTheWebGuy · · Score: 5, Funny

      Why is this necessary?

      It's gnecessary kuz it's kool.

      --
      bash: rtfm: command not found
    2. Re:I'm sure many will ask this... by adler187 · · Score: 2, Insightful

      The same could be said for a lot of Windows applications using the Win prefix and Mac OS X apps using the i prefix.

    3. Re:I'm sure many will ask this... by zapp · · Score: 4, Interesting

      This has all been gone over before, but it isn't new to kde/gnome.

      X*, win* go back farther probably.

      I think it's both a style thing (recognizable 'gAIM, on that must be AIM for gnome'), and also it makes it easy to tell what works with what. xemacs clearly is the X version of emacs. winamp clearly doesn't work on linux or mac, and konquerer clearly doesn't work on gnome.

      --
      no comment
    4. Re:I'm sure many will ask this... by Azureflare · · Score: 4, Interesting
      So we know easily what WM libraries a package requires without looking at the depends.

      Personally I don't like it when packages don't prepend their names with k or g if they are specifically for KDE or Gnome. It's annoying when you try to install it and it says it wants to install gnome libraries, or KDE libraries (whichever WM libraries you don't like installing, maybe both if you're limited on HD space)

      It's consistent, and it works. It may seem a bit lame sometimes, but it makes things really easy for me (And others).

      Also from an ease of use standpoint, it makes it easy to know what to expect from a package. "Oh, that has a k before it, that means I'll be seeing KDE themes on that app if I'm running XFce."

      Sure, we should probably have a unified theme so things are pretty seamless and you can't tell if something is for KDE or Gnome (or more specifically, using qt or gtk). But we're not there yet, and it would be really confusing if we didn't keep things the way they are.

      I think eventually a distro will successfully make it possible for all apps to look similar to each other in all WM, and I think it would be a good thing to do that.

    5. Re:I'm sure many will ask this... by Scarblac · · Score: 2, Insightful

      and also it makes it easy to tell what works with what. xemacs clearly is the X version of emacs.

      That's a perfect example of what is wrong with this approach. The difference between emacs and xemacs has nothing to do with X; yet everybody seems to think so. Both of them work fine under X. Xemacs just forked off ages ago because of disagreements with RMS.

      --
      I believe posters are recognized by their sig. So I made one.
  7. Re:screenshot? by boarder8925 · · Score: 2, Informative
  8. kst by Anonymous Coward · · Score: 5, Informative

    It looks good, but I'm skeptical about its usefulness for me. ROOT already produces damn good output and fills most of my needs. And for everything else there's gnuplot.

    But I will look at kst. If it's as good as they say it is, I may use it instead of gnuplot.

    1. Re:kst by drauh · · Score: 2, Informative

      ugh. root is a 300 lb gorilla, and about as friendly: c++ is its scripting language. gnuplot is good, but you have to work hard to make pretty plots. also, it is missing a 'plot data as image' (i.e. a pixel or rectangle per point) feature. as someone else has mentioned above, mayavi is great.

      --
      This is a tautology.
    2. Re:kst by Lust · · Score: 2, Informative

      Don't forget Octave, a Matlab-like but free data analysis/plotting program. It can directly run most of what you've already programmed for Matlab.

  9. Another one? by drsmack1 · · Score: 5, Funny

    We need to stop creating all of these astrophysics programs for Linux and develop the ones we have now!

    1. Re:Another one? by ajs · · Score: 2

      Wow, drsmack1, I'd like to appologize on behalf of the moderators who were clearly drinking when the modded you.

      Folks: he was making a joke... you know "another window manager?!", etc., etc....

      The moderation flag you were looking for was "funny"

  10. He'll need it... by Chemical+Serenity · · Score: 4, Funny

    ... to plot how quickly his site gets slashdotted. ;)

    --
    "People will pay big bucks for the luxury of ignorance."
  11. I would have thought Gnome by Anonymous Coward · · Score: 4, Funny

    I thought they were looking to find the Grand Gnunified Theory.

  12. Comment removed by account_deleted · · Score: 5, Insightful

    Comment removed based on user account deletion

  13. Instructions by jsweval · · Score: 2, Funny

    Anyone else not able to read the instructions because its MIME type is text/html?

  14. Python Announces Fork... by Eberlin · · Score: 4, Funny

    Pst (pronounced pissed...or post, depending on who you ask) is a Python fork of the now-popular kst program. Instead of astrophysics, it endeavors to plot a graph of aggression among IT employees.

    Finding absolutely no funding from anyone, including government agencies, the project has taken a life of its own among overworked volunteer developers. These Pst programmers work dilligently on the code while concurrently providing enough test data to plot.

    Due to its popularity, a port using Microsoft Foundation Classes is in the works. Rumor has it that it will be called MFT (pronounced miffed). A C port is also being made -- and their sourceforge project is located at ifuckinhateusers.sourceforge.net

  15. Ever since Igor by PaSTE · · Score: 4, Informative

    I used <a href="https://www.wavemetrics.com">Igor</a&g t; as an undergrad for most of my data plotting and graphing (physics), but the interface was not intuitive and without knowing the command-line language, navigating the menus took a very long time, even when you knew what you were looking for. Also, the price ($400 for the latest version) kept me away from using it off campus. Now I tend to stick to <a href="http://root.cern.ch/">ROOT</a> simply because its Cint interpreter is ideal for handling the massive (10^6 n-tuples) amount of data I look over, and because it's free. However, making advanced graphs and plots with ROOT requires a whomping manual and a fairly good grasp of C, as there are virtually no point-and-click features to it. I'm really glad another open-source data manipulation program is in the works, and that it can do the things ROOT can as easliy as Igor can without the emense price restrictions.

    --
    /*No comment*/ #No comment //No comment ;No comment 'No comment REM No comment !No
    1. Re:Ever since Igor by Compuser · · Score: 2

      Repeat after me: Matlab is your friend.

    2. Re:Ever since Igor by infolib · · Score: 2, Interesting

      However, making advanced graphs and plots with ROOT requires a whomping manual

      Why not try R? There's not much point and click, but the command are quite ok, and as you can see from their page it generates some VERY good-looking graphs. Its GPL'ed :-)

      --
      Any sufficiently advanced libertarian utopia is indistinguishable from government.
  16. Grace (aka Ace/gr) by nsushkin · · Score: 3, Informative
    Why reinvent the wheel, what was wrong with using Grace.

    While I agree that the Motif app looks a little outdated, the app is free as in GPL and is really powerful in terms of features. For example, it allows scripting.

    1. Re:Grace (aka Ace/gr) by Satai · · Score: 2, Informative

      I like the scripting in Grace, but it had quite a learning curve. I found that the python bindings were useful. For scripted plots, supermongo (not free) is popular, but I think Grace is prettier.

    2. Re:Grace (aka Ace/gr) by tskisner · · Score: 3, Insightful

      I'm one of the grad students that uses kst every day for analyzing data for the Boomerang experiment.

      Try using Grace to plot 1e6 data samples from 16 different sources in real time as it is acquired. Grace has some nice math features, but I believe that within the next year most of these will be surpassed by the features of kst.

      Sometimes it's easier to build a new house that renovate an old one ;-)

  17. Re:An interesting take on the GPL by aeoo · · Score: 2, Interesting

    For the uninformed ones like me, why exactly are you required to sign an NDA? Isn't science based on sharing information? What am I missing here? How can a researcher be told how to run their research? I don't understand where that power comes from.

  18. Re:An interesting take on the GPL by pyite · · Score: 2, Interesting

    Can't do research without money (for the most part). Can't get published unless you have credibility. Can't have credibility unless you have peer review. Can't have peer review unless you have peers. Can't have peers unless you're at a University from which you get funded.

    --

    "Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman

  19. Re:An interesting take on the GPL by 0racle · · Score: 2, Informative

    Because without it, your not doing the research. Essentially its because they said so, you can take it or leave it.

    --
    "I use a Mac because I'm just better than you are."
  20. Not quite... by DarkMan · · Score: 5, Informative

    I take your point - most of this application, like many, is in principle doable independant of the underlying OS.

    However, there are a few pluses on the side of Linux for this application.

    2 GB+ files. Some versions of Win32 can do them, some can't. Some can only do it with a following wind. When you're talking scientific data, such file sizes can crop up often, if not a regular feature.

    Network independance. This is less of an issue for display, but on the processing side, being able to coordinate multiple tasks, spread across many servers, from one desktop is a big win. Particualrly when it's a 'free' side effect (requires no extra programming). Four boxes are cheaper than a quad box - by quite a sizeable margin.

    Which leads us on to the scheduler - with Win2K, a background number crunch task will take longer than on Linux, and impact interactive response more. That's not off the top of my head - that's based off my Linux/KDE desktop and my office mates Win2K systems doing the same tasks (computational chemistry, so essentially big matrix sums).

    There's also library support. Not such a big one, as they can be ported, but it's more work that way. By libraries, I mean things like FFTW, LAPACK and BLAS.

    So, that's a few areas with modest wins for unix/KDE. I'll add that headless admin for Unix is simpler than for Windows, which helps with the headless cruncher boxes, and conclude that there is a reason that unix is popular in universities, as it's got a slight edge.

    Yes, it may well have been as easy to write for Win32 as KDE [0] - but in use, the linux is better for the number crunching.

    [0] I wouldn't agree to that personally, but there's a degree of personal preference in there, so that's not objective.

  21. Where the name comes from by greppling · · Score: 4, Informative
    From the tutorial:

    Q: What does kst stand for?

    A: The 'k' in kst stands for the same thing as the K in KDE. (ie, the letter after J and before L). The 's' and the 't' have a similar explanation.

  22. Re:Funding by updog · · Score: 3, Interesting
    You may be trolling, but that is an interesting question - there are definitely arguments for releasing it as BSD licensed. I don't agree at all with the moderators for modding the comment as Flamebait.

    Here's one reason to make it GPL - it makes financial sense. Since they have invested money and time into this project, they should strive to maximize their potential return.

    By making it GPL, their initial investment can be improved upon by anyone, and the Kst project can reap the benifits.

  23. Re:An interesting take on the GPL by 0racle · · Score: 2, Informative

    "THEY" are whomever "YOU" are dealing with. It may be the "U." if they are the "THEY" that wishes to keep the ownership and anything related to the project, or perhaps "THEY" refers to the sponsor if technically "YOU" are working for "THEY" through the "U." In short "THEY" is whomever is asking you to sign the "NDA."

    --
    "I use a Mac because I'm just better than you are."
  24. Re:Funding by aussersterne · · Score: 2, Insightful

    You mean like your tax-funded congress, your tax-funded police department, or your tax-funded internal revenue service?

    --
    STOP . AMERICA . NOW
  25. Gretl by Knights+who+say+'INT · · Score: 2, Informative

    Another piece of software that became quite a hit in academia is Gretl, the GNU Econometrics, Time-series and regression library.

    It's a perfect clone of eViews, and it's free as in "just grab it"

  26. Comment removed by account_deleted · · Score: 2, Informative

    Comment removed based on user account deletion

  27. Gnuplot? by bsd4me · · Score: 2, Interesting

    Can anyone comment on this compared with Gnuplot?

    LaTeX and Gnuplot got me through college without having to pay for laser printing papers (the laser printers on the unix machines were free, but the ones on the PCs and Macs were a nickel a page.).

    --

    (S(SKK)(SKK))(S(SKK)(SKK))

  28. Openness in academia by baxissimo · · Score: 3, Informative

    People share their ideas and publish, because if they don't they don't get tenure or graduate or whatever. But there's often a big development investment involved in going from some paper published in a journal to working code. The published paper may give you the major differences between what they've done and the previous work, but most any important achievement builds on a bunch of prior work which is, say, contained in 5 other papers, which in turn were each based on 5 other papers each, and tracking all that down and getting it and translated into code can take a long time.

    So say I'm the guy who published the paper -- while you're spending all your time re-implementing my previous method, I've already gone on and developed another few enhancements or a whole new method, and gotten another paper or two out of it, while you're still trying to recreate what I did last year.

    So basically, just because the ideas in academia are basically open, that doesn't mean the implementations are. In fact, I've heard some math guys voice the opinion that releasing your source code is just a waste. It takes a significant time investment on your part to get it all packaged up, perhaps cleaning up the code some, and then to answer questions people have about it etc. And when it comes time for tenure review, they don't ask you how much source code you released. No, all that matters is how many journals you published in. So while you were busy cleaning up your source code for release, fixing non-critical bugs and adding non-essential features, you could have been working on the next publication instead.

    Of course a lot of researchers do go all the way with openness and release source. But I've seen plenty of both strategies.

    Another part of the equation is that Universities these days all want a piece of the action on anything invented within their walls. So they want you file for patents and such, and try to find people that will license those patents. And naturally a big cut of the licensing fees go to the Universtity. And then there's folks who dream of starting their own multi-million dollar spin-off technology company, so they don't want to let too many details about what they're doing to leak out until they've got all the patents lined up.

    1. Re:Openness in academia by starsong · · Score: 2, Insightful

      In fact, I've heard some math guys voice the opinion that releasing your source code is just a waste. It takes a significant time investment on your part to get it all packaged up, perhaps cleaning up the code some, and then to answer questions people have about it etc. And when it comes time for tenure review, they don't ask you how much source code you released.

      This makes absolute sense, if the goal in academia is the same as it is in corporate life: to make the most money and to be at the top of the food chain. On the one hand, people go into science claiming they're not in it for the money (and usually, there *isn't* that much money in it), but will hoard knowledge and backstab viciously to increase their position in the hierarchy. Why bother? They're just trading one type of greed for another.

      I don't want to come off sounding completely naive, but I don't think cleaning code up, packaging it, sharing it with the world and answering questions is a waste of time. Similarly, it makes me sad that some professors view courses and lectures as an burdensome part of their job requirement.

      No, all that matters is how many journals you published in. So while you were busy cleaning up your source code for release, fixing non-critical bugs and adding non-essential features, you could have been working on the next publication instead.

      This really drives me nuts. It's the tragedy of the commons, on a smaller scale. Don't spend time teaching others when you could be advancing your own status. Chances are someone else will choose not to, and get ahead of you! Why help other people when you can put that energy into your own work? Hell, why do we even teach grad students? Before you know it, they have degrees and are competition! So be sure not to teach your Ph.D. students too much. And take their papers and put your name on them. And make sure your undergraduate lectures are boring as hell. That will slow them down.

      As for the volume of papers, yes, "publish or perish." Yes, publication is incredibly important in science, and you'll fall flat on your ass if you don't make it a top priority. But the point is to share knowledge as well as get your name in print. Which means that the papers you write should actually SAY something. I think there's something seriously wrong with a system that rewards professorial diva-ism and 1-month publication intervals over sharing knowledge. Maybe this is why we now have hundreds of boring, poorly-written, dubiously constructed papers pouring out of every journal with a logo and a printing press. I'm not doing that much work right now and even so I can barely keep up with it. I don't even want to think about how many the peer reviewers chucked out before publication. Unless you actually have something interesting to say, it's just wasted time.

      Hopefully, if the current trend keeps up, people will eventually stop evaluating by number of publications and start looking at their contents and impact. And who knows, maybe they'll even look at other things too.

  29. Comment removed by account_deleted · · Score: 2, Insightful

    Comment removed based on user account deletion

  30. Re:Funding by PitaBred · · Score: 3, Insightful

    How about because they chose Qt as the toolkit because it makes development easier, and Qt is GPL licensed, so derivatives have to be?
    Dumbass.

  31. ROOT? by lightray · · Score: 2, Informative

    You know all those "Segmentation Fault" errors that ROOT gives you?

    A real tool doesn't do that.

    It's really very cute how enamored particle physicists are by C++. It's very fitting it turns every software construct into something they're familiar with, a particle! er, object. Too bad they can't ditch the FORTRAN habits.

    "You can write bad FORTRAN in any language." - my advisor