[Architecture] C4A: Tasks for review meeting

Kasper Markus kasper at raisingthefloor.org
Fri Jan 16 07:55:36 EST 2015


Hi Claudia,

We can change it to

  "conditions": [
{
"type": "http://registry.gpii.net/conditions/inRange",
*"max": 400000,*
"min": 400,
"inputPath": 
"http://registry\\.gpii\\.net/common/environment/visual\\.luminance"
}
]

That should catch any value above 400. The way it's currently 
implemented, not specifying a max (or min for that matter) means that 
it's open ended on that side.. But making a big enough value for max 
should have the same effect in practice.

~Kasper



On 1/16/15 1:07 PM, Claudia Loitsch wrote:
> Hi Kasper,
>
> Am 13.01.2015 11:25, schrieb Kasper Markus:
>> Hi Claudia,
>>
>> Thanks for the pull request! I've merged it in now with the following 
>> changes:
>>
>>   * Changed tabs to 4*spaces to ensure formatting is similar across
>>     editors
>>   * Updated the conditions block to what in my knowledge is the most
>>     current/correct format
>>
>> A diff of my changes can be seen here:
>>
>> https://github.com/GPII/universal/commit/e712bd948bffca45ca4c6220de4d532ec55271b0
>>
> I`ve tested if your change to the condition block still work with the 
> RBMM and I found a minor issue:  As you know, the RBMM cannot handle 
> arbitrary specifications of conditions as they are not yet defined. 
> For the review I`ve just implemented one possible condition spec - one 
> that includes a min and a max value. Your spec contain only a min 
> value.  Can we change this from:
>
> https://github.com/GPII/universal/blob/review3/testData/preferences/vladimir.json#L68-L73
>
> to
>
>  "conditions": [
> {
> "type": "http://registry.gpii.net/conditions/inRange",
> *"max": 400,*
> "min": 400,
> "inputPath": 
> "http://registry\\.gpii\\.net/common/environment/visual\\.luminance"
> }
> ]
>
> If this causes to much trouble on your end, I can also make a change 
> in the RBMM. However, inRange indicates that we have at least 2 values.
>
> Cheers,
>
> Claudia
>
>
>> Cheers,
>> ~Kasper
>>
>> On 1/12/15 2:23 PM, Claudia Loitsch wrote:
>>> Hi Kasper,
>>>
>>> Happy new year!!!!
>>>
>>> I`ve created a pull request as desired:
>>>
>>> https://github.com/GPII/universal/pull/306
>>>
>>> I`ll update the Wiki page accordingly: 
>>> http://wiki.gpii.net/w/Year_3_Review_Integration_Roadmap_%28C4A%29
>>>
>>> Cheers,
>>>
>>> Claudia
>>>
>>>
>>> Am 06.01.2015 15:57, schrieb Kasper Markus:
>>>> Hi Claudia,
>>>>
>>>> Happy new year and thanks for your response!
>>>>
>>>> In terms of all the changes, would you be able to do a pull request 
>>>> to the review3 branch of GPII universal repo? That makes it easier 
>>>> to see what changes are made, and gives us a record for 
>>>> bug-tracking in case something suddenly isn't working as expected..
>>>
>>>
>>>
>>>>
>>>> A few comments inline below
>>>>
>>>>
>>>> On 12/23/14 4:17 PM, Claudia Loitsch wrote:
>>>>> Hi Kasper,
>>>>>
>>>>> Please, find attached again the complete and updated set of 
>>>>> preferences and installed solutions both scenarios: Vladimir and 
>>>>> Subway.
>>>>>
>>>>> Some comments below:
>>>>>
>>>>> Am 22.12.2014 15:10, schrieb Kasper Markus:
>>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>>
>>>>>> There are several last minute things that still need to happen 
>>>>>> before the review in January. For details, please see the wiki 
>>>>>> page: 
>>>>>> http://wiki.gpii.net/w/Year_3_Review_Integration_Roadmap_%28C4A%29
>>>>>>
>>>>>>
>>>>>> Specifically, these are the outstanding tasks:
>>>>>>
>>>>>>
>>>>>> Claudia:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Mouse trails should be on for the Vladimir lobby scenario
>>>>>>
>>>>> *CL: Changed the value in the N&P accordingly: 
>>>>> https://github.com/Cloud4AllTUD/RuleBasedMatchMaker_RESTful_WS_Maven/blob/4e27b43d14289f1b18709cdcec67bb274db73733/src/main/webapp/WEB-INF/testData/preferences/vladimir.json#L10 
>>>>> *
>>>>
>>>> I tested the mouse trailing again and it still didn't seem to work. 
>>>> After a bit of playing around, it seems that the value range of 
>>>> mouseTrailing is 0..10, so anything above that value will be 
>>>> ignored (and mouse trails will be off).
>>>>
>>>>
>>>>>> 1.
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     NP set for subway
>>>>>>
>>>>> *CL: attached: vladimir/vladimir.json => condition block noise: 
>>>>> https://github.com/Cloud4AllTUD/RuleBasedMatchMaker_RESTful_WS_Maven/blob/4e27b43d14289f1b18709cdcec67bb274db73733/src/main/webapp/WEB-INF/testData/preferences/vladimir.json#L37-L76*
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Create NP sets for Li and the two devices
>>>>>>
>>>>> *CL: attached: classroom/li.json => including both NP sets: 
>>>>> "default" and "turn-down-light"*
>>>>>
>>>>>> 1.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Claudia and Nick:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Device reporter file for the classroom scenario
>>>>>>
>>>>> *CL: attached: classroom/installedSolutionClassroomAndroid.json 
>>>>> and classroom/installedSolutionClassroomWindows.json*
>>>>>
>>>>>> 1.
>>>>>>
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Run through the classroom scenario and ensure all users are
>>>>>>     working as expected
>>>>>>
>>>>> *CL: done! *
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Ensure RBMM supports screen resolution
>>>>>>
>>>>> *CL: done!*
>>>>>
>>>>>   * However, the URI for the screen resolution hack should
>>>>>     be*.net.* *It is currently .org. :
>>>>>     **https://github.com/GPII/universal/blob/review3/testData/preferences/dispres1024x768.json#L12*
>>>>>
>>>> Nice catch! Thanks! I will update accordingly!*
>>>>
>>>> *
>>>>>
>>>>>   * Furthermore, I cannot handle the absence of preference values.
>>>>>     That has no meaning for us. Therefor I added *"is**Active**":
>>>>>     true for the screen reolution app-specific preference*:
>>>>>     https://github.com/Cloud4AllTUD/RuleBasedMatchMaker_RESTful_WS_Maven/blob/4e27b43d14289f1b18709cdcec67bb274db73733/src/main/webapp/WEB-INF/testData/preferences/chrisWindows.json#L10-L11*
>>>>>     *
>>>>>
>>>>
>>>> Ok, that makes sense to me!
>>>>
>>>>>   * **
>>>>>
>>>>>> 1.
>>>>>>
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Set magnification factor for Li in Supernova
>>>>>>
>>>>> *CL: That should work. I don´t see a mistake here when running the 
>>>>> tests. *
>>>> Hmmm.. I dont quite remember what the issue was.. Do you, Nick? 
>>>> Perhaps if you try launching supernova manually, then setting 
>>>> magnification to 1.0x and also turning it off, and save/quite 
>>>> supernova.. Then try using Li again and see if it works correctly?
>>>>
>>>> Thank again Claudia,
>>>>
>>>> ~Kasper
>>>>
>>>>
>>>>
>>>>>
>>>>> Cheers and Merry Christmas,
>>>>>
>>>>> Claudia
>>>>>
>>>>>> 1.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Guti:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Full integration of the Chrome Extension including the
>>>>>>     settings handler
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Test the Chrome Extension with the Vladimir review scenario,
>>>>>>     the rule based match maker, and the other installed solutions.
>>>>>>
>>>>>>
>>>>>> Christophe:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Windows and Linux install instructions
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Give the RWG settings for Franklin to Claudia
>>>>>>
>>>>>>
>>>>>> Kasper:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     PCP/FM integration
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Merge context reporting work related to the subway scenario
>>>>>>
>>>>>> 3.
>>>>>>
>>>>>>     Update the cloud based FM for the classroom scenario
>>>>>>
>>>>>> 4.
>>>>>>
>>>>>>     Create ‘reset’ tag for classroom scenario
>>>>>>
>>>>>> 5.
>>>>>>
>>>>>>     FM part of CAS
>>>>>>
>>>>>>
>>>>>> Tomas:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Test the review scenario for DTV, Vladimir and STMM
>>>>>>
>>>>>>
>>>>>> Jasmin:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Ticket vending machine integration
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Test the review scenario with the big ticket machine
>>>>>>
>>>>>> 3.
>>>>>>
>>>>>>     Ensure we have a video connection and a back up solution in
>>>>>>     case it fails
>>>>>>
>>>>>>
>>>>>> Javi:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Merge ticket vending integration into the review branch
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Andriod setup instructions for the subway scenario
>>>>>>
>>>>>> 3.
>>>>>>
>>>>>>     Environment reporter on Android
>>>>>>
>>>>>>
>>>>>> Andres:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Implement the mini-matchmaker and integrate it
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Implement the automatic generation of conditions in MMM
>>>>>>
>>>>>> 3.
>>>>>>
>>>>>>     Integrate the twitter client
>>>>>>
>>>>>> 4.
>>>>>>
>>>>>>     Integrate the environmental reporter
>>>>>>
>>>>>> 5.
>>>>>>
>>>>>>     Run through the Vladimir subway scenario
>>>>>>
>>>>>>
>>>>>> Ferran:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Test MA in the classroom scenario for ‘Chris’ and ‘Li’
>>>>>>
>>>>>>
>>>>>> Guillem:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Implement the context aware server
>>>>>>
>>>>>>
>>>>>> Nick:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Ensure Virtual Magnifying Glass can be entered in SAT
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Run through the developer scenario and ensure everything is
>>>>>>     working
>>>>>>
>>>>>>
>>>>>> Kostas:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Describe how and where to include the PMT and PCP code
>>>>>>
>>>>>>
>>>>>> Thanos:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Include PMT/PCP in the installer and update instructions
>>>>>>
>>>>>>
>>>>>>
>>>>>> I won’t be available until January, so please make sure you make 
>>>>>> use of the lists if you have any questions or need any help.
>>>>>>
>>>>>>
>>>>>> Thanks everyone! 
>>>>>
>>>>> -- 
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>> Dipl.-Medieninf. Claudia Loitsch
>>>>>
>>>>> Technische Universität Dresden
>>>>> Fakultät Informatik
>>>>> Institut für Angewandte Informatik
>>>>> Professur für Mensch-Computer Interaktion
>>>>> 01062 Dresden
>>>>> Tel.: +49 351 463-42025
>>>>> Fax : +49 351 463-38491
>>>>> E-Mail:claudia.loitsch at tu-dresden.de
>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> Architecture at lists.gpii.net
>>>>> http://lists.gpii.net/cgi-bin/mailman/listinfo/architecture
>>>>
>>>
>>> -- 
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> Dipl.-Medieninf. Claudia Loitsch
>>>
>>> Technische Universität Dresden
>>> Fakultät Informatik
>>> Institut für Angewandte Informatik
>>> Professur für Mensch-Computer Interaktion
>>> 01062 Dresden
>>> Tel.: +49 351 463-42025
>>> Fax : +49 351 463-38491
>>> E-Mail:claudia.loitsch at tu-dresden.de
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> Architecture at lists.gpii.net
>>> http://lists.gpii.net/cgi-bin/mailman/listinfo/architecture
>>
>>
>> -- 
>> Kasper Galschiot Markus
>> Lead Research Engineer,
>> Raising the Floor - International,
>> www.raisingthefloor.org
>>
>>
>> _______________________________________________
>> Architecture mailing list
>> Architecture at lists.gpii.net
>> http://lists.gpii.net/cgi-bin/mailman/listinfo/architecture
>
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dipl.-Medieninf. Claudia Loitsch
>
> Technische Universität Dresden
> Fakultät Informatik
> Institut für Angewandte Informatik
> Professur für Mensch-Computer Interaktion
> 01062 Dresden
> Tel.: +49 351 463-42025
> Fax : +49 351 463-38491
> E-Mail:claudia.loitsch at tu-dresden.de
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


-- 
Kasper Galschiot Markus
Lead Research Engineer,
Raising the Floor - International,
www.raisingthefloor.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gpii.net/pipermail/architecture/attachments/20150116/b8c420e3/attachment-0001.html>


More information about the Architecture mailing list