Christian Zimmermann writes
> I emailed him already.
I email him prolly immediately when I saw it, and I think I was
up when it arrived.
> It has to do with when the server was down and I
> could not retrieve the data. I had a test for that, and it failed partially.
??? I don't remember it being down but
root@katri ~ # uptime
04:11:40 up 18 days, 9:59, 1 user, load average: 354.47, 354.33, 353.97
suggests it was. Anyway I am supposed to move to new server.
--
Cheers,
Thomas Krichel http://openlib.org/home/krichel
skype:thomaskrichel
L. Colin Xu writes
> I think there is likely a bug on computing "closeness measure" and
> "betweenness measure" in coauthorship network. I had always been in
> top 1% for many months, suddenly this month it is ranked around
> 20,000.
I think
http://collec.repec.org/nodes/x/u/2.html
has your current ranking at source in CollEc. It can change
every day.
--
Cheers,
Thomas Krichel http://openlib.org/home/krichel
skype:thomaskrichel
Reminder.
On Fri, 8 Feb 2019, Christian Zimmermann wrote:
> On Thu, 7 Feb 2019, Thomas Krichel wrote:
>
>> Christian Zimmermann writes
>>
>>> I am expecting to speak early May at a meeting of network economists.
>>
>> What meeting exactly? If I see what they work on, maybe I can see
>> if I have technology to offer.
>>
>
> A meeting of young economists working on networks. I expect them to have a
> sophisticated knowledge, thus saying you Dijkstra's algorithm is not
> sufficient. They will want details.
>
>>> I will talk about CollEc, and how this can be used to study
>>> networks. People likely will want to know some details about the
>>> computations. If you have any details I can share beyond what is on
>>> http://collec.repec.org/doc.html, they would be welcome.
>>
>> I could spruce up that document for the occasion. If you send me a
>> list of questions that would be helpful.
>>
>>> I will make a pitch for volunteers. Maybe I can find someone interested
>>> in
>>> helping with CollEc.
>>
>> Up for grabs if somebody wants to take it over. Rewriting it in
>> Python would not be hard because the web interfaces is
>> written in XSLT, so you don't have to redo that. In fact
>> it would probably be quite easy to redo the computations
>> in Python, and leave the search in Perl.
>>
>>
>> --
>>
>> Cheers,
>>
>> Thomas Krichel http://openlib.org/home/krichel
>> skype:thomaskrichel
>>
>
