![]() ![]() INSTEAD Apple are going to direct Mac users to download exactly what we have here: XQuartz, the source project for X11. It is in fact a big, frustrating PITA to use X11 successfully! But the rewards are a lot of fun.ĪLSO NOTE: Apple are no longer going to provide X11 with Mac OS X! It come with the Mac OS X 10.8 Mountain Lion installer. It takes unfathomable patience to use X11 because it is designed by geeks for geeks, not for average or even intermediate users. I also have unfathomably patience setting up this geek level stuff. But I am a geek and I have taken the time to learn how to use this. Don't write a one star review out of ignorance. If you don't know what X11 is, if you don't know what MacPorts are or what Fink/Porticus/PortAuthority/Pallet are, then don't download XQuartz. It requires knowledge of using the CLI found in the Terminal app for full capability. The XQuartz project is typically well ahead of what Apple provide. This is where Apple contributes to and sources what they provide with Mac OS X as X11. > load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_csm.This IS X11. > load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/gsn_code.ncl" > Anyone else having this issue? Anyone know a work around, other than my current work around of plotting to another type and viewing that? > All other plot types are fine, just x11 has issues. > I thought maybe it was a XQuartz issue but ncl 6.0 plots fine which leads me to think its 6.1 and Xquartz or also likely my installation of 6.1 though the same issue is occurring when run from a remote linux machine and run locally on my mac. I upgraded to 10.8 a few days ago (perhaps foolishly), since this upgrade when I plot to x11 within NCL I get a half drawn plot as below, this occurs with maps and plain contours, it seems that the first step is being plotted then it forgets to do the rest. > I think this is more of an NCL issue rather than an XQuartz (X11) issue. > On Aug 2, 2012, at 1:00 PM, Alan Brammer wrote: > If you are using a MacOS 10.6 binary, you might consider trying one of our 10.7 binaries, which we only have for NCL V6.1.0-beta. When you say 10.8, I assume you mean MacOS? Which NCL binary are you using? ![]() ![]() > On Aug 3, 2012, at 10:25 AM, Mary Haley wrote: > My DISPLAY variable is set to "/tmp/launch-IyDvMq/:0" > Another user said they were experiencing similar issues, so hopefully its not just my own wrong doings. May be that XQuartz has subtly changed something that had been updated in the latest release. This problem occurs when run locally and on a remote system, so I don't think its an installation issue, but rather some difference in how 6.1 talks to X11 compared to the older versions of NCL. I updated my NCL installation to the 10.7 binary albeit to no avail. > I did mean Mac OS 10.8 (Mountain Lion). On Aug 5, 2012, at 1:45 PM, Alan Brammer wrote: ![]() Let me know if you continue to have issues, and I'll file a ticket on this. I did google this issue, and read that every time you do a system update, that you need to reinstall XQuartz. We've always used Apple's default X11 server. I should have mentioned earlier that we've never actually tested NCL with XQuartz explicitly, so it doesn't surprise me that there could be issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |