Cross Logbook

my Poisson simulation

2010-03-19T04:57:00.001+00:00

my Poisson simulation

2010-03-19 12:21:02

# -*- coding:utf-8 -*-
"""
Created on 2010-3-18

@author: Cross
"""
from scipy.stats import poisson

p1 = poisson(1.725)
p2 = poisson(0.935)
margin_HAD = 1.12
margin_HILO = 1.08

psize = 100000


a1 = p1.rvs(psize)
a2 = p2.rvs(psize)

h=0
d=0
a=0
HI = 0
LO = 0

for i in range(psize):
    if a1[i]>a2[i]:
        h = h + 1
    elif a1[i]        a = a + 1
    else:
        d = d + 1

    if a1[i] + a2[i]<2 .5:=".5:" br="br">        LO = LO + 1
    else:
        HI = HI + 1


print "======================="
print "HDA"
print 1/margin_HAD/(h/float(psize))
print 1/margin_HAD/(d/float(psize))
print 1/margin_HAD/(a/float(psize))
print "======================="
print "HILO 2.5"
print 1/margin_HILO/(LO/float(psize))
print 1/margin_HILO/(HI/float(psize))

possion function example (from scipy)

2010-03-08T17:58:00.001+00:00

>>> from scipy.stats import poisson, lognorm >>> myShape = 5;myMu=10 >>> ln = lognorm(myShape) >>> p = poisson(myMu) >>> ln.rvs((10,)) generate 10 RVs from ln array([ 2.09164812e+00, 3.29062874e-01, 1.22453941e-03, 3.80101527e+02, 7.67464...... http://bit.ly/9MkbZC

导出豆瓣日记到其他Blog和twitter

2010-02-26T04:57:00.001+00:00

导出日记到其他blog：豆瓣日记 -> twitterfeed -> ping.fm -> blogger/wordpress 导出广播到twitter：豆瓣广播 -> feedburner -> twitter (->facebook) 豆瓣广播到新浪微博：豆瓣广播 -> google reader (add star) stared -> 新浪微博（关联博客） http://bit.ly/dpOErL

[Blog post] python reads excel

2010-01-11T01:12:00.001+00:00

python reads excel

crossz | January 11, 2010 at 1:12 am | Tags: python tutorial howto | Categories: life | URL: http://wp.me/pthU9-hH

Use the excellent xlrd package, which works on any platform. That means you can read Excel files from Python in Linux! Example usage:

Open the workbook

import xlrd wb = xlrd.open_workbook('myworkbook.xls')

Check the sheet names

wb.sheet_names()

Get the first sheet either by index or by name

sh = wb.sheet_by_index(0) sh = wb.sheet_by_name(u'Sheet1')

Iterate through rows, returning each as a list that you can index:

for rownum in range(sh.nrows):     print sh.row_values(rownum)

If you just want the first column:

first_column = sh.col_values(0)

Index individual cells:

cell_A1 = sh.cell(0,0).value cell_C4 = sh.cell(rowx=3,colx=2).value

(Note Python indices start at zero but Excel starts at one)

Add a comment to this post

WordPress.com | Thanks for flying with WordPress!

Manage your subscriptions | Publish text, photos, music, and videos by email using our Post by Email feature. | Signup with WordPress.com

HOWTO: backup / resotre mysql database for drupal

2009-12-05T08:12:00.002+00:00

To Backup:

select the database need backup in phpMyAdmin
select the tab of Export, and save as file in a sql format.

To resotre:

upload the drupal installation files into the proper directory.
copy the old director of /site/all, in which are the modules and themes to the new site directory. Otherwise some functionalities will miss.
create the database you want in phpMyAdmin with proper database name.
select the new database and Import.
Install the new drupal site.

HOWTO install egg file for python

2009-10-14T20:52:00.002+01:00

Using easy_install, which is installed by setuptools (http://pypi.python.org/pypi/setuptools).

~$ easy_install XXXXX.egg
This is for binary egg file. While script egg file should be treated as normal shell script. To install:
~$ sh XXXXXX.egg

#######################
Another popular way to install python 'modules', is:
~$ python setup.py install
This is from python source. Normally third parties will provide such kind of source.

HOWTO: screencast in Ubuntu

2009-09-10T19:32:00.003+01:00

With recordmydesktop, ffmpeg, mencoder, libavcodec-unstripped-52 ( for aac audio encoder), ubuntu-restricted-extras installed. Run the following command to record and convert it to mp4 format, in order to upload to youtube.

recordmydesktop
mencoder out.ogv -oac pcm -ovc lavc -lavcopts vcodec=mpeg4 -o out.mp4

Matlab: Mex example in C way

2009-08-20T02:13:00.003+01:00

There is a yprime.c for mex in Matlab. Here I translate to C, in order to understand mex better.

#include <math.h>
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
static void yprime(
double* yp,
double* y
)
{
double r1,r2;

double mu = 1/82.45;
double mus = 1 - 1/82.45;

r1 = sqrt((y[0]+mu)*(y[0]+mu) + y[2]*y[2]);
r2 = sqrt((y[0]-mus)*(y[0]-mus) + y[2]*y[2]);

yp[0] = y[1];
yp[1] = 2*y[3]+y[0]-mus*(y[0]+mu)/(r1*r1*r1)-mu*(y[0]-mus)/(r2*r2*r2);
yp[2] = y[3];
yp[3] = -2*y[1] + y[2] - mus*y[2]/(r1*r1*r1) - mu*y[2]/(r2*r2*r2);
return;
}

int main(){
double yo[4];
double yi[4] = {100, 2, 3, 4};

yprime(yo, yi);
printf("print out %f",yo[0]);

// some conversion practice
double a = yi[0];
char t1[7],t2[8],t3[8];

*t1= (char) a;
strcpy(t2,t1);

printf(strcat(t1, t2));

gcvt(a,7,t3);
puts(t3);

// i = sprintf(str, "%d", 15); //for interger to string

return 0;
}

HOWTO: compile objective-c using gcc in Linux

2009-08-16T18:24:00.003+01:00

to compile these examples of objective-c (install libobjc first) from objective-c on wikipedia.org

1) traditional:
gcc -c XX.m XXX.m -Wno-import
gcc -o prog XX.o XXX.o -lobjc -Wno-import

2) gcc *.m -lojbc -Wno-import

Note:
-Wno-import is because the maintainer of gcc doesn't like 'import';

-lobjc: -l(library) -L(libaray directory) -lobjc(for GNU objective-c libraray)

For those examples using GNUstep, most of the header files need to be changed from ' #import ' to '#import ' to suit the GNU objective-c library.

More details: http://www.cs.indiana.edu/classes/c304/oop-intro.html

HOWTO: Version control using BZR vs RCS

2009-08-03T21:25:00.007+01:00

No matter programming or documents editing, BZR will work for you to provide easier and better version control.

Here are some simple steps for docs processing:
======================

bzr init
create a folder, 'text', then create a file, 'test1.txt', in which we type in a paragraph. Then 'bzr init' to let bzr know this is the folder where bzr should monitor.
bzr add
'bzr add test1.txt'. Now bzr knows where and what to monitor.
bzr diff
add more text into the test1.txt, then run 'bzr diff' to test whether there is any changes.
bzr commit -m 'description'
if there are some changes, and you want to create another version for that for the current version backup. run 'bzr commint -m "some description"'.
bzr log
to check verisons.
...
more changes and more commits here.
...
bzr branch -r
For example we just want to retrive the first version, run 'bzr branch `pwd` -r 1'. A new folder with the name of current folder 'text' will be created, in which our text1.txt 1st version is there.

RCS: (same procedure)
===================

create folder RCS
this step can be ignored, the rcs information will be saved in the same folder with the file you are editing. Otherwise, the file info file will be saved in the RCS folder.
ci -u test1.txt
ver 1.1 is created. RCS uses the concept of 'lock'. -l -r -u are similar, to keep the text file locked when new version is registered.
co -l test1.txt
(if without this step, new version can not be registered. because 'no lock', prompted by 'ci', is this for synchronization?) So to lock the text file to make it writable (very weird concept, locked == writable???). Then add more text in it.
rcsdiff test1.txt
To check what's different from the registered version.
ci -u test1.txt (same with step2)
The version number increment with 0.1.'ci -r2 -u test1.txt' to make the version increment by 1.0.
...
more changes and more commits here.
...
co -l1.1 test1.txt
Retrive version 1.1 to replace the current editing file. -l -r -u are similar, just -u makes the file non-writeable, while -l make the file writeable. Good practice is 'ci -u' and 'co -l', so that when the new version is registered by ci, the file will become 'non-writable'='can not modify'='No lock'. (weired)

Note: no space between '-r2' and '-u1.1'.

Conclusion:
==================
BZR is more user friendly, and Ubuntu uses it on launchpad.net.
RCS is quite mature (old), LYX uses it as version control. So even I don't like it, but I have to still use it, because I love Lyx.

HOWTO: autoconf & automake HELLO WORLD

2009-08-02T20:43:00.006+01:00

1) Create sources, “Makefile.am”
2) `autoscan`：create configure.scan
3) Rename “configure.scan” to “configure.ac”
4) `autoheader`:create config.h.in for automake
5) Add AM_INIT_AUTOMAKE to “configure.ac”, just after AC_INIT()
6) `aclocal`:create necessary macros in aclocal.m4 for automake.
7) `automake --add-missing --copy`: create Makefile.in from Makefile.am
8) `autoconf`:create configure
9) `./configure`:check and create Makefile
10) `make`
11) `make install`

if you modify your source...
1) Run `autoscan` again
2) Compare configure.scan with configure.ac
* Update configure.ac
3) Run `autoreconf`

***********************
# Makefile.am for hello.c
bin_PROGRAMS=hello
hello_SOURCES=hello.c
***********************

To simplify it:
===============
1) c/cc files, Makefile.am
2) autoscan => mv configure.scan configure.ac => add Add AM_INIT_AUTOMAKE after AC_INIT

3) autoheader
4) aclocal
5) automake

6) autoconf <=> autoscan,(compare configure.ac),autoreconf

7) ./configure && make && make install

Simplest 'make'
=====================
Hello.c:

#include
int main(int argc, char* argv[])
{
printf("Hello, world!\n");
return 0;
}

Makefile:

# Makefile: A standard Makefile for hello.c
all: hello
clean: rm -f hello

Run: make, to create executable bin file.

HOWTO: autoconf & automake

2009-08-02T16:21:00.002+01:00

Write makefile.am templates.
Write configure.in.
2.1 Use autoscan to generate a template.
2.2 Specialize the generated configure.scan to suit your project.
2.3 Rename configure.scan to configure.in.
Run automake to generate Makefile.in from Makefile.am (automake scans configure.in to find out more about the project).
Run aclocal to make local copies of all autoconf macros. These macros are then included in the project.
Run autoconf to generate configure.

=========================

automake
automake, when used in conjunction with autoconf, makes creating Makefiles easy. automake operates on a Makefile.am to generate Makefile.in . Makefile.in is then processed by the configure script to generate Makefile. Makefile.am has macros that are processed by automake. A sample Makefile.am is shown below. Variables surrounded by @'s are automatically propagated without change to Makefile.in. The configure script, when parsing Makefile.in into Makefile, makes the necessary substitutions (for example, @LDFLAGS@ may get expanded to "-lm -lthread).

  bin_PROGRAMS = gpstat
  gpstat_SOURCES = about.c interface.c multi-plot.c attach_process.c
  gpstat_LDFLAGS = @LDFLAGS@ @GTK_LIBS@ -lgthread
  INCLUDES = @GTK_CFLAGS@

automake knows the rules to create object files and executables for the platform it is running on. The above sets of macros tell automake that:
1. The final executable is to be named gpstat.
2. The sources for gpstat are the value of gpstat_SOURCES.
3. Add @LDFLAGS@, @GTK_LIBS@, and -lgthread to the link line. (The configure script will replace LD_FLAGS and GTK_LIBS with their proper values.)
4. Include the variable $INCLUDES in the compilation line.

=========================

autoconf

The configure script is generated from configure.in using autoconf. configure.in is a normal text file that contains several autoconf macros. These macros specify what tests to carry out. General uses of the configure script include:
1. Find machine information (Hostname, version...).
2. Find the path to a particular program (bison, lex, ...).
3. Find out if a tool supports a feature (for example, if the compiler supports bool).
4. Check if the required libraries are available on your system.
5. Process Makefile.in to generate Makefile.

=========================================

automake also provides autoscan, a utility script that will help you create a template configure.in. autoscan scans the program sources and adds suitable macros to configure.in. It creates configure.scan, which then should be renamed configure.in, after making suitable modifications.
automake also provides a program called aclocal. aclocal makes local copies of all autoconf macros, so that other developers can modify the configure.in file.

You can combine the invocation of automake, aclocal, and autoconf as follows:
foo@pastwatch$ aclocal&& automake && autoconf

Sample:
Comments can either begin with dnl or a #. The following is a small, well-documented, self-explanatory configure.in file.
#============================start configure.in============================
dnl Process this file with autoconf to produce a configure script.
dnl notice how comments are preceded by "dnl"
# comments can also begin with a #
dnl This macro is a must, and this tests if the configure
dnl script is running in the correct directory
AC_INIT(src/about.c)
dnl This macro tells the configure script to put
dnl "defines" in a file rather than the command line.
AM_CONFIG_HEADER(config.h)
dnl get the flags
CFLAGS="${CFLAGS=}"
dnl this macro is used to get the arguments supplied
dnl to the configure script (./configure --enable-debug)
dnl Check if we have enable debug support.
AC_MSG_CHECKING(whether to enable debugging)
debug_default="yes"
AC_ARG_ENABLE(debug, [ --enable-debug=[no/yes] turn on debugging
[default=$debug_default]],, enable_debug=$debug_default)
dnl Yes, shell scripts can be used
if test "x$enable_debug" = "xyes"; then
CFLAGS="$CFLAGS -g -DDEBUG"
AC_MSG_RESULT(yes)
else
CFLAGS="$CFLAGS -O3 -ffast-math -mcpu=v8 -mtune=ultrasparc"
AC_MSG_RESULT(no)
fi
dnl tells us that we require autoconf with version greater than
dnl 2.12 to generate configure
AC_PREREQ(2.12)
dnl get system information
AC_CANONICAL_SYSTEM
dnl Since foo is currently untested on any os other
dnl than solaris, so check the os and quit if not solaris.
UNSUPPORTED_OS="FOO is currently unsupported on your platform.
If you are interested in making it work on your platform, you are
more than *welcome*. Contact foo@bar.sun.com for details."
case "${target_os}" in
solaris*)
echo ===========================================================
echo Setting up build environment for ${target_cpu}${target_os}
echo ===========================================================
;;
*)
AC_MSG_ERROR($UNSUPPORTED_OS)
esac

# Build time sanity check...
AM_SANITY_CHECK
dnl get path to install program
AC_PROG_INSTALL
AC_ARG_PROGRAM
VERSION=0.1
PACKAGE=foo
dnl initialize automake
AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
dnl Checks for c compiler.
AC_PROG_CC
dnl check for standard c headers
AC_HEADER_STDC
dnl export these variable (so Makefile substitutions
dnl can be made.
AC_SUBST(CFLAGS)
AC_SUBST(LDFLAGS)
dnl Checks for libraries.
dnl AC_CHECK_LIB(gthread, g_thread_init)
dnl AC_CHECK_LIB(pthread, pthread_create)
dnl Check for /proc
AC_CHECK_FILE(/proc,,AC_MSG_ERROR(Cannot
find /proc. See the file 'README' for help.))
dnl check for procfs.h
AC_CHECK_HEADER(procfs.h,,
AC_MSG_ERROR(Cannot
find procfs.h. See the file 'README' for help.))
dnl Checks for header files.
AC_CHECK_HEADERS(fcntl.h)
AC_CHECK_HEADERS(time.h)
dnl Checks for typedefs, structures, and compiler characteristics.
AC_C_CONST
AC_TYPE_PID_T
dnl Create these files, making substitutions if necessary
AC_OUTPUT([
src/Makefile
Makefile
]
)
#============================end configure.in============================

HOWTO: get stdin from shell in Gedit External Tool

2009-07-28T00:56:00.005+01:00

The following code can get the input from Gedit External Tool as you assigned for 'input'.

#!/bin/bash
search=`xargs`
echo $search

The trick is the command of xargs.

Also available Environment Variables in Gedit External Tool are:
=====================
GEDIT_CURRENT_DOCUMENT_URI
GEDIT_CURRENT_DOCUMENT_NAME
GEDIT_CURRENT_DOCUMENT_SCHEME
GEDIT_CURRENT_DOCUMENT_PATH
GEDIT_CURRENT_DOCUMENT_DIR
GEDIT_DOCUMENTS_URI
GEDIT_DOCUMENTS_PATH

An example: compile java file and run it
=========================
javac $GEDIT_CURRENT_DOCUMENT_NAME && java -cp . `echo $GEDIT_CURRENT_DOCUMENT_NAME | sed s/.java//`

16-bit binary data interpreting difference between Java and Matlab

2009-07-22T12:13:00.003+01:00

The 16-bit data will be interpreted as different values in Java and Matlab. WHY??

Here are some experiments: save number 15 to 8-bit and 16-bit binary files, and another 259 in 16-bit binary files (refer to : this post).
======================

In Matlab (fread(fid1, 'uint8');): 15

16 bit bin file containing 15:
In WinHex: 0F 00
In java (DataInputStream.readShort();): [3840, 0]
=> 3840/256=15;
=> so, it's a kind of [15 00]
In Matlab (fread(fid1, 'uint16');): 15

16 bit bin file containing 259:
In WinHex: 03 01
In java (DataInputStream.readShort();): [769, 0] //Note, for every byte, java can

contain a value larger than 256, while other programming language will increment.
=> 769%256 = 1; 769/256=3.0039;
=> so, it's a kind of [03 01]
In Matlab (fread(fid1, 'uint16');): 259

Therefore:
========================
Therefore, a integer value in the range of 16-bit, for example 41837. In Matlab,

it will be intepreted as 41837, mod(41837,256)=109, 41837/256=163.4. So 41837 can

be displayed as [163 109] = 163*256+109; while java intepret [163 109] as

163+109*256 = 28067;

Conclusion:
========================
This seems wrong inside Java, but Java know how to process such value and export

it correctly to another bin file, which one can be understood by Matlab, WinHex or

other programming languages or editor.

Simplest procedure to TRIPLE BOOT on Macbook

2009-07-21T09:44:00.003+01:00

The must:

Only ONE partition for Linux; Only ONE partition for Windows. (to satisfy Windows)
Windows must locates at the last partition. (to satisfy Macbook)
Before installing, ensure the partitions are ready and good! (Disk Utility normally can not do this, or do half of this task. Because it will create several 'spare spaces' between each partitions made by it, these partitions always make the Windows installation fail due to more than 4 primary partitions existing. But Disk Utility can create one more partition from the original one whole partition, then split it using other ways, which includes 'diskutil' in Mac, 'gparted' from Linux Livecd or even the Windows installer during Windows setup). Any partitions modification will make Windows can not boot up even synced by rEfit.
- If Windows has been installed by Boot Camp. Try to change boot.ini in my windows partition (disk util create a new partition between mac and windows and messed up my boot.ini, the partition it tried to boot (third) is now linux Hd instead of windows (become 4th. This might be your problem. It gave me BSoD right after splash screen)

So the procedure:

Partitioning (DO NOT USE BOOT CAMP ASSISTANT)
sync mbr/gpt using rEfit. (maybe can be ignored)
Install Winxp on the 4th (last) partition.
sync mbr/gpt using rEfit.(maybe can be ignored)
Install Linux.

Java/Matlab read and write 16-bit data file

2009-07-21T00:32:00.006+01:00

Read 16 bit binary file:

File file = new File("FILENAME.bin");
FileInputStream fis = new FileInputStream(file);
BufferedInputStream bis = new BufferedInputStream(fis);
DataInputStream dis = new DataInputStream( bis );

short[] myarray = new short[256000];
int cnt;
for (cnt = 0; cnt < 256000; cnt++) {

myarray[cnt] = dis.readShort();

}
fis.close();

Alternatively:
RandomAccessFile dis = new RandomAccessFile(new File("FILENAME.bin"), "r");

Note:
1) bufferedInputStream can be ignored, but it will improve the performance 90% for large file operation.
2) RandomAccessFile works like a 'pointer', similar to fread in Matlab, offset or skip can be assign when data retrieving while not really load all the file. This class has both read and write methods, it is a convenience class, like filereader and filewriter, while the former method is kinda low level methods.
Write 16 bit binary file:
FileOutputStream fos = new FileOutputStream(new File("OUTPUT.bin"));
BufferedOutputStream bos = new BufferedOutputStream(fos);
DataOutputStream dos = new DataOutputStream(bos);

for (cnt = 0; cnt < 256000; cnt++) {

myarray[cnt] = dis.readShort();

}

bos.flush();

fos.close();

Alternatively:
RandomAccessFile dos = new RandomAccessFile(new File("OUTPUT.bin"), "rw");
Note: The following step is essential!!!! Otherwise, there will be some data lost.
bos.flush();
Matlab:

fid1 = fopen('filename.bin', 'r');
A = fread(fid1, 100, 'uint16=>float32');
fclose(fid1);

fid2 = fopen('output.bin', 'w');
fwrite(fid2, A, 'uint16');
fclose(fid2);

BUG, HOWTO: how java read 8-bit and 16-bit

2009-07-19T18:50:00.009+01:00

you have to use twice as much memory, but there really is no other solution:
=======================

use a short to hold an unsigned byte, use a long to hold an unsigned int. (And use a char to hold an unsigned short.)
This example create a 16-bit file, which only contain a value, 15 in 16-bit (000f), This file can be viewed by Gedit. From Matlab, it can retrieve and display correctly as 15, but in Java, using DataInputStream.readShort(), it's 3840, which equals to 15*256.

Example 1: Using Matlab to generate a 16-bit data file.
================
clear;clc;%% create binA=15;fid = fopen('output.bin', 'w'); fwrite(fid, A, 'uint16');fclose(fid);%% read binfid1 = fopen('output.bin', 'r'); B = fread(fid1, 1, 'uint16')fclose(fid1);

Example 2: Using Java to retrive the 16-bit data from the bin file.
===========
import java.io.*;public class convbin { public static void main(String args[]) throws IOException { File file = new File("onev.bin"); FileInputStream fis = new FileInputStream(file); BufferedInputStream bis = new BufferedInputStream(fis); DataInputStream dis = new DataInputStream( bis );// RandomAccessFile dis = new RandomAccessFile(new File("fotech1.bin"), "r"); short[] myarray = new short[256000]; int cnt; for (cnt = 0; cnt < 1; cnt++) { myarray[cnt] = dis.readShort(); } fis.close(); System.out.println("Done."); FileOutputStream fos = new FileOutputStream(new File("o22.bin")); BufferedOutputStream bos = new BufferedOutputStream(fos); DataOutputStream dos = new DataOutputStream(bos);// RandomAccessFile dos = new RandomAccessFile(new File("o22.bin"), "rw"); for (cnt = 0; cnt < 1; cnt++) { dos.writeShort(myarray[cnt]); } System.out.println("Finish."); bos.flush(); fos.close(); }}

More details, except the example: http://www.darksleep.com/player/JavaAndUnsignedTypes.html

HOWTO: run remote X11 applications

2009-07-17T17:33:00.005+01:00

The server is running on Linux. To run the remote server applications on my own machine:

On Windows:
=======================
1. Install Xming as the X11 server.
2. Run Putty, as ssh client, with the X11 forwarding arguments: 'localhost:0' or ':0', or even with blank only enable forwarding.
On Mac OSX
=======================
1. run: ssh -X -l username 192.168.1.XXX
* using Putty: with the X11 forwarding arguments: ':0'!!!!!!!!
On Linux
=======================
1. run: ssh -X -l username 192.168.1.XXX
* using Putty: with the X11 forwarding arguments: ':0' or blank.

HOWTO: install Adobe Air on Feodra 11

2009-07-12T23:07:00.002+01:00

Just guest Redhat developers want to improve the boot speed, they make the fedora 11 without some 'useful' packages by default. This makes some program can not installed properly, such as Adobe Air.

The fix:
================

yum -y install xterm gtk2-devel gnome-keyring libxml2-devel libxslt rpm-devel nss

From: yum -y install xterm gtk2-devel gnome-keyring libxml2-devel libxslt rpm-devel nss

放弃在Mac 10.5.7 上安装GNUstep 0.23

2009-07-12T11:26:00.002+01:00

经过大半个星期的下班时间调试，尝试在Mac osx 10.5.7 （darwin 9.7）上安装GNUstep 0.23，最终没有成功，还把Mac弄残一次，我猜可能是由于compiling的时候出现的segmentation fault致使Kernel Panic。

总结失败教训如下：

make的时候，常常是需要 $LDFLAG 比用到 $DYLD_LIBRARY_PATH 的时候多。后者貌似更像是运行程序的时候使用，而不是configure和make时候用。
Mac作为操作系统，其界面无可争议，但是底层系统方面，我个人觉得还不如Linux。在最近的console下编译程序的时候，出现两次致使Mac不断重启的情况，而解决方法都是不得不重装系统后，第二次更离谱，连cmd＋s的single user mode都无法进入。Mac啊，现在给我的感觉是典型的外强中干。
GNUstep需要有gnu的objc runtime，如果用默认的设置，必然使得其调用mac自带的gcc和objc的库，这样肯定会带来些兼容性的问题。我猜我弄出的两次mac无法开机不断重启，与此两种不兼容并冲突的objc有关系。因为GNUstep在ubuntu 9.04和fedora 11下编译运行的很好。如果想在Mac上安装，我觉得还得是要等macports提供，macports跟进的还算不错，对gnustep，和官方新版本放出的时间也就差2个星期左右。可是，macports下的objc目前还不能安装，等到这个出现后，可以再试编译gnustep源文件。

以下是我用到的env设置：

#export LDFLAGS='-L/usr/local/lib -L/usr/lib -L/opt/local/lib -L/sw/lib'

export LDFLAGS='-L/opt/local/lib -L/sw/lib -L/usr/GNUstep/Local/Library/Libraries'

#export DYLD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/opt/local/lib:/sw/lib

export CPPFLAGS='-I/opt/local/include -I/sw/include'

#export CFLAGS='-I/usr/local/include -I/usr/include -I/opt/local/include -I/sw/include'

export PATH=/opt/local/bin:/opt/local/sbin:/sw/bin:/sw/sb:/usr/bin:/bin:/usr/sbin:/sbin

#. /usr/GNUstep/System/Library/Makefiles/GNUstep.sh

注：个人认为，在编译gnu的程序时，最好避免用到mac自带的一些命令。而且，最好在编译之前，把/usr/bin/gcc改成是 /opt/local/bin/gcc-mp-4.2这样的，以防止避免gnu和mac的程序冲突。

HOWTO: remove files older than N days

2009-07-09T00:07:00.002+01:00

Command Syntax

find /path/to/files* -mtime +5 -exec rm {} \;

Note that there are spaces between rm, {}, and \;

Usage:
======================
Extremely useful for Miro, because it doesn't delete files unwatched. So with this command added in /usr/bin/miro, the Miro library will keep only latest videos no matter you watch it or not.

Explanation
=======================
The first argument is the path to the files. This can be a path, a directory, or a wildcard as in the example above. I would recommend using the full path, and make sure that you run the command without the exec rm to make sure you are getting the right results.
The second argument, -mtime, is used to specify the number of days old that the file is. If you enter +5, it will find files older than 5 days.

The third argument, -exec, allows you to pass in a command such as rm. The {} \; at the end is required to end the command.

Command from: http://www.howtogeek.com/howto/ubuntu/delete-files-older-than-x-days-on-linux/

HOWTO: compile source code on MAC OS X

2009-07-07T22:33:00.006+01:00

Conditions:

======================

Macport (recommended, can be found on apple.com, updated and organized well) and Fink are installed in default locations, /opt/local and /sw.

Note: Fink is buggy, normally reinstallation on the previous version will not work, issues like path setup maybe occur, either bin files or libraries are not accessible.

To compile:

======================

For library invoking:
export LDFLAGS='-L/usr/local/lib -L/usr/lib -L/opt/local/lib -L/sw/lib'
- '-L/dir' is the convention to setup gcc switch, while -L for make is --check-symlink-times, useless for me :)
- Official way for invoking library is to setup $DYLD_LIBRARY_PATH (export DYLD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/opt/local/lib:/sw/lib), which in Linux is $LD_LIBRARY_PATH by default.
- Normally lib path don't need specified, because the bin files (in /usr/bin or /opt/local/bin' will know where to get appropriate libraries, no matter bin files from Macports or Fink.
For header files invoking:
export CPPFLAGS='-I/usr/local/include -I/usr/include -I/opt/local/include -I/sw/include'
- This is the way to setup both 'make' and 'gcc' switch, which is 'make -I/usr/local/include'.

Example:

=====================

The following are what I typed in terminal with user root to compile GNUstep-0.22.

export CPPFLAGS='-I/usr/local/include -I/opt/local/include'

export LDFLAGS='-L/usr/local/lib -L/usr/lib -L/opt/local/lib -L/sw/lib'

export DYLD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/opt/local/lib:/sw/lib:/usr/GNUstep/Local/Library/Libraries

. /usr/GNUstep/System/Library/Makefiles/GNUstep.sh

MAC OS X: change the environment PATH

2009-07-05T21:22:00.002+01:00

To add a new directory to the path, simply add it to the existing PATH line in .profile being careful to separate it from other directories there with colons and careful not to introduce unwanted spaces (everything after the space will be ignored). For example, to add the directory /mightyq/bin to the PATH shown above, the line could become any of the following examples:

export PATH=/mightyq/bin:/opt/local/bin:/opt/local/sbin:$PATH export PATH=/opt/local/bin:/mightyq/bin:/opt/local/sbin:$PATH export PATH=/opt/local/bin:/opt/local/sbin:$PATH:/mightyq/bin

Note that in the third example the new directory is added to the end of the PATH. You have the ability to optimize the searches your shell will do on your behalf each time you run a command by organizing your PATH logically. Putting less frequently used or really massive directories later in the path may give you a little performance boost (although these days things are pretty fast, so you have to be a little anal to really enjoy this).

If you don’t need a directory in your path, you can reverse the process by deleting the unwanted directory still taking care to preserve the no spaces, colon separation rules.

One last note, to test the change you made, you can use the echo command, but you need to make the shell reload the .profile first. Assuming you are in your home directory (if not, running ‘cd’ without any options will take you there), run these commands:

. ./.profile echo $PATH

The first . is a shortcut to cause the shell to ’source’ or load the contents of the subsequent file as itself, in the manner that the shell uses when you login to a system or start a Terminal window. If you simply executed these commands like a shell script (bash .profile, for example) you would start a new shell, that shell would get the variable set, and at the end of running the .profile script, that new shell would cease to exist and the newly defined variables would be relegated to the missing sock universe.While . makes the variables generated from new shell ( child shell ) return to the current shell (parent shell).

BUG: GNUstep Project Center can not generate the conf for 'MAIN_MODEL_FILE'

2009-07-04T18:12:00.002+01:00

GNUstep Project Center (0.5.0) can not generate the conf for 'MAIN_MODEL_FILE', therefore, to make the GUI (gorm style) work, put corresponding configuration in the 'GNUmakefile'. Like the following:

#
# Main application
#

PACKAGE_NAME=SimpleApp

APP_NAME=SimpleApp
SimpleApp_MAIN_MODEL_FILE=MainMenu.gorm

The missing part in Gorm Manual on GNUstep, about 'NewClass' controller

2009-07-04T15:12:00.002+01:00

8 Creating an Application
If you have ProjectCenter, you need to open it and create an “Application” project.
Create it with the name “FirstApp”. From there you can open the MainMenu.gorm by
clicking on interfaces and selecting MainMenu.gorm. If Gorm.app is properly installed, you
Gorm should start up.
If you don’t have ProjectCenter, you can create the Gorm file by hand. First you need
to start Gorm. You can either do this by doing ‘gopen Gorm.app’ from a command line
prompt, or you can invoke it from the Dock or from the workspace’s file viewer.
You then need to select the ‘Document’ menu, and then ‘New Application’. This should
produce a new document window, with a menu and an empty window. This should be
the same as with the ProjectCenter gorm file since this is the basic starting point for an
application.
For the sections below... only do one or the other, not both.
8.1 Creating A Class In Gorm
There are two ways to do this next operation. I will take you through each step by step.
First click on the classes icon in the toolbar on the top of the Gorm document window.
You should see the view below change to an outline view containing a list of class names.
Once this happens we’re ready to create a class. Select the class you wish to subclass in
the outline view. For our example we will use the simplest: NSObject. Select it by clicking
on the class name once. Then go to the Classes menu in the main menu and select Create
Subclass (you can also type Alt-Shift-c, which will do this as well. The new class will be
created in the list with the name “NewClass”.
8.2 Using The Outline View
From here double click on the subclass name to make it editable. Type the name of the
class and hit enter. For our example, please use the class name MyController. When you
hit enter an alert panel will appear and warn you about breaking connections, simply select
OK and continue.
This method of inputting the classes was inspired by IB in OPENSTEP 4.2/Mach which
had functionality very similar to this. For users of that the transition to Gorm will be
seamless.
8.2.1 Adding Outlets In The Outline View
Too add an outlet, select the round icon with the two horizontal lines in it (it sort of looks
like a wall outlet. This should become depressed. Here you need to go to the Gorm Menu,
under Classes select “Add Outlet/Action”. Each time you press this menu item another
outlet will be added with a name similar to newOutlet, as you add more the number at the
end will increase. For now add only one outlet.
To rename the outlet simply double click it and change it’s name like you did the class
above to “value” for the sake of our example.
Chapter 8: Creating an Application 20
8.2.2 Adding Actions In the Outline View
The procedure to add on action is precisely the same as adding an outlet, except you
must click on the button which looks like a target (a circle with a + inside). Add an action
and name it “buttonPressed:” for the sake of our example.
8.3 Using The Class Edit Inspector
This way is much more inline with the “OPENSTEP/GNUstep” philosophy. For each
object there is an inspector, even for Class objects.
Once you have created the class as described in the previous section “Creating a Class
In Gorm”, you must skip to this section to use the inspector. In the Gorm main menu
select Tools and then select “Inspectors”. This will make certain that the inspectors win-
dow is being displayed. Once the inspectors window is up move the pulldown on the top
to “Attributes” and select the class you created which should, at this point, have the name
“NewClass”. You’ll notice that the “Class” field at the top which shows the name’s back-
ground color has turned white, instead of grey. This indicates that this class name is
editable. Erase “NewClass” from the text field and type “MyController”.
8.3.1 Adding Outlets In The Inspector
Adding outlets is very intuitive in the inspector. Simply select the “Outlets” tab in the
tab view and click “Add” to add more outlets, and “Remove” to remove them. For the sake
of our example, add one outlet and name it “value”.
8.3.2 Adding Actions In the Inspector
Very much like above only with the “Actions” tab, add an action called button pressed.
8.4 Instantiating The Class
In the Classes outline view select the new class you’ve created, now called MyController
and then go to the Gorm menu and select Classes, and then Instantiate. The document
window should shift from the classes view to the objects view. Amoung the set of objects
should be a new object called MyController.
8.5 Adding Controls from the Palette
Go to the Gorm menu and select Tools, then Palettes. This will bring the palette window
to the front. The second palette from the left is the “ControlsPalette”. Select that one and
find the button object (it should have the word “Button” in it). Drag that to the window
and drop it anywhere you like.
Repeat this operation with the text field. It’s the control with “Text” in it. We are now
ready to start making connections between different objects in the document.
Chapter 8: Creating an Application 21
8.5.1 Making Connections
The type of application we are creating is known as a “NSApplication delegate” this
means that the MyController object will be set as the delegate of NSApplication.
To make this connection click on NSOwner and hold down the Control button, keep it
pressed as you drag from the NSOwner object to the MyController object. The inspectors
window should change to the Connections inspector and should show two outlets “delegate”
and “menu”. Select the “delegate”, at this point you should see a green S and a purple T
on the NSOwner and MyController objects respectively, and press the “Connect” button
in the inspector. In the “Connections” section of the inspector you should see an entry
which looks similar to “delegate (MyController)” this indicates that the connection has
been made.
Now we need to make connections from the controller to the textfield and from the
controller to the button. Select the MyController object and Control-Drag (as before)
from the object to the text field, this will make an outlet connection. You should see the
connections inspector again, this time select the “value” outlet and hit Connect.
Next, control-drag from the button to the controller, this will make an action connec-
tion. The connections inspector should again appear. This time you need to select the
“target” outlet, to get the list of actions. The list should have only one entry, which is
“buttonPressed:” since this is the one we added earlier. Press Connect. You should see an
entry like “buttonPressed: (MyController” in the Connections section of the inspector.
It is also possible to make this connection to NSFirst, but to keep things simple, make
it directly to the object. If you make the connection to buttonPressed: on NSFirst the
functionality of the application will be unchanged, but the invocation will take the path
described above in the section which describes “The Responder Chain”.
8.6 Saving the gorm file
At this point you must save the .gorm file. Go to the Gorm menu and click Documents
and then select “Save”. If the document was opened from a pre-existing .gorm, it will save
to that same file name. If it is an UNTITLED .gorm file a file dialog will appear and you
will need to select the directory where you want to store the .gorm file and type the name
of the .gorm file.
8.7 Generating .h and .m files from the class.
This is different than saving, some people have gotten this confused with the idea of
Gorm generating the code for the gui. Gorm does nothing of the sort (grin).
Go to the Classes section in the Document window and select the MyController class yet
again. Now go to the Gorm menu and select Classes and the select “Create Class Files”.
This will bring up a file panel and it allow you to select the directory in which to put the
files. It will first create the MyController.m file and then the MyController.h file. Simply
select the directory in which your app will reside and hit okay for both. You can change
the names, but the default ones, which are based on the class name, should be sufficient.

When you look at the .m for this class, you should see the ‘buttonPressed:’ method with
the commecnt ‘/* insert your code here */’ in it. Delete this comment and add ‘[value
setStringValue: @‘‘Hello’’];’. The class should look like this after you’re done:
/* All Rights reserved */
#include
#include "MyController.h"
@implementation MyController
- (void) buttonPressed: (id)sender
{
[value setStringValue: @”Hello”];
}
@end
You recall, we connected the textfield to the “value” variable. The call above causes the
method setStringValue to be invoked on the textfield you added to the window.
Also, note that the name of the method is “buttonPressed:”. This is the action which is
bound to the button. When it is pressed the text in the textfield should change to “Hello”.
You now need to build the application either by copying in a GNUmakefile and making
the appropriate changes or by using ProjectCenter’s build capability, depending on if you
use it or not.
This app is available as “SimpleApp” in the Examples directory under the Documen-
tation directory distributed with Gorm. Hopefully this has helped to demonstrate, albeit
on a small scale, the capabilities of Gorm. In later chapters we will cover more advanced
application architectures and topics.

Cross Logbook

my Poisson simulation

my Poisson simulation

possion function example (from scipy)

导出 豆瓣 日记 到其他Blog和twitter

[Blog post] python reads excel

python reads excel

HOWTO: backup / resotre mysql database for drupal

HOWTO install egg file for python

HOWTO: screencast in Ubuntu

Matlab: Mex example in C way

HOWTO: compile objective-c using gcc in Linux

HOWTO: Version control using BZR vs RCS

HOWTO: autoconf & automake HELLO WORLD

HOWTO: autoconf & automake

HOWTO: get stdin from shell in Gedit External Tool

16-bit binary data interpreting difference between Java and Matlab

Simplest procedure to TRIPLE BOOT on Macbook

Java/Matlab read and write 16-bit data file

BUG, HOWTO: how java read 8-bit and 16-bit

HOWTO: run remote X11 applications

HOWTO: install Adobe Air on Feodra 11

放弃在Mac 10.5.7 上安装GNUstep 0.23

HOWTO: remove files older than N days

HOWTO: compile source code on MAC OS X

MAC OS X: change the environment PATH

BUG: GNUstep Project Center can not generate the conf for 'MAIN_MODEL_FILE'

The missing part in Gorm Manual on GNUstep, about 'NewClass' controller

导出豆瓣日记到其他Blog和twitter