[ 
https://issues.apache.org/jira/browse/MAHOUT-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965572#comment-13965572
 ] 

Alex commented on MAHOUT-1505:
------------------------------

so following the discussion, here's an example proposal, 

top_terms is an array of single-element objects, because they are ordered, 
c is an object of term,weight pairs, as is r,
points is an object of point objects, where each point object has the point 
coordinates, vector_name, and weight.

{noformat}
{
"top_terms": [
  {"action":2.43}, 
  {"adherence":1.5}
],
"cluster":"VL-10515",
"n":5924,
"c": 
  {
   "action":0.023, 
   "adherence":0.223, 
   "administration":0.011 
  }
,
"r":
 { 
   "action":0.446, 
   "adherence":1.501,
   "administration":0.306 
 },
"points": 
{ 
 { "point": 
     {
      "action":3.2,
      "adherence":4.1,
      "administration":1.3
     }
   "vector_name":"/reut2-000.sgm-100.txt",
   "weight":"1.0"
 },
 { "point": 
    { 
      "cat:1.2,
      "dog":4.4,
      "administration":0.3
    }
  "vector_name":"/reut2-000.sgm-101.txt",
  "weight":"1.0"
 }
} 

}
{noformat}

thoughts?

> structure of clusterdump's JSON output
> --------------------------------------
>
>                 Key: MAHOUT-1505
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-1505
>             Project: Mahout
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 0.9
>            Reporter: Terry Blankers
>            Assignee: Andrew Musselman
>              Labels: json
>
> Hi all, I'm working on some automated analysis of the clusterdump output 
> using '-of = JSON'. While digging into the structure of the representation of 
> the data I've noticed something that seems a little odd to me.
> In order to access the data for a particular cluster, the 'cluster', 'n', 'c' 
> & 'r' values are all in one continuous string. For example:
> {noformat}
> {"cluster":"VL-10515{n=5924 c=[action:0.023, adherence:0.223, 
> administration:0.011 r=[action:0.446, adherence:1.501, 
> administration:0.306]}"}
> {noformat}
> This is also the case for the "point":
> {noformat}
> {"point":"013FFD34580BA31AECE5D75DE65478B3D691D138 = [body:6.904, 
> harm:10.101]","vector_name":"013FFD34580BA31AECE5D75DE65478B3D691D138","weight":"1.0"}
> {noformat}
> This leads me to believe that the only way I can get to the individual data 
> in these items is by string parsing. For JSON deserialization I would have 
> expected to see something along the lines of:
> {noformat}
> {
>     "cluster":"VL-10515",
>     "n":5924,
>     "c":
>     [
>         {"action":0.023},
>         {"adherence":0.223},
>         {"administration":0.011}
>     ],
>     "r":
>     [
>         {"action":0.446},
>         {"adherence":1.501},
>         {"administration":0.306}
>     ]
> }
> {noformat}
> and:
> {noformat}
> {
>     "point": {
>         "body": 6.904,
>         "harm": 10.101
>     },
>     "vector_name": "013FFD34580BA31AECE5D75DE65478B3D691D138",
>     "weight": 1.0
> } 
> {noformat}
> Andrew Musselman replied:
> {quote}
> Looks like a bug to me as well; I would have expected something similar to
> what you were expecting except maybe something like this which puts the "c"
> and "r" values in objects rather than arrays of single-element objects:
> {noformat}
> {
>     "cluster":"VL-10515",
>     "n":5924,
>     "c":
>     {
>         "action":0.023,
>         "adherence":0.223,
>         "administration":0.011
>     },
>     "r":
>     {
>        "action":0.446,
>        "adherence":1.501,
>        "administration":0.306
>     }
> }
> {noformat}
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to