Bug Report

What is the expected behavior?

To wiki show the correct way to be used now.

What is the current behavior?

I updated to latest beta 24, and saw that $media got deprecated, but docs still shows the old way for listening for MediaChange (using it).
I couldn't find a way to get the asObservable from MediaObserver that is not from $media like it shows in changelog.

Platform

• Android

Author or host

Host

Version of SDK

1.2.6

Details

For the attached card json.
The button in the column set is cutoff on android

The same card on web
![image](https://user-images.githubusercontent.com/51158485/76822819-25366300-6838-11ea-9e0c-be

When computing the isosurface, when 4 simplex edges crosses the isosurface, we add 2 triangles to the isosurface triangulation.

Right now we add these arbitrarily (in these 3 lines) but we should add them so that the curvature is minimized.

The current state o

The relationship of pg_hint_plan Rows hints and aqo should be explored and documented, and if there is a dependency of the order of aqo and pg_hint_plan in shared_preload_libraries, this should be documented also.

We should have a setup so that way the DAE initialization algorithm's default tolerances match those from solve. That would require a setup for delayed tolerance changes.

The Chef Input variables need documentation.
https://github.com/SCOREC/core/blob/develop/phasta/phInput.h

Please donate your time. Documenting as few as two variables a day can prevent an innocent Chef user from seg-faulting.

We are using this page as a starting point for the variable descriptions:
https://fluid.colorado.edu/wiki/index.php/Chef:_Mesh_Partitioning#Chef

I tend to think that beta1 and beta2 are off. I think that beta1=0.4 and beta2=0.1 may be better defaults than what we have right now, but this would need extensive testing. That's a very high gain but right now we rarely ever reject, and are usually 10-100x below the error estimate we are aiming for.

So I took the example (adaptive) And tried my hand at setting it up for NES games. (I set it up for mario first)

But I get this error. I have a feeling it's related to those inputs and outputs at the top of the python file.

The input coordinates and the output coordinates. I didn't really understand them so I don't know how to set it up for NES (if that's even the issue at all)

It would be great to add Doxygen or similar for auto-generation of documentation and start a push towards standardisation of the style and comment/description data as to work with such a system.

Followed by a discussion with @franasa , @bussec; we have come up with the below schema for cell object.

Cell:
    discriminator: AIRR
    type: object
    required:
        - cell_id 
        - rearrangements  
        - virtual
    properties:
        cell_id:
            type: string
            description: >
                Identifier defining the cell of origin for the q

The simple test in the README doesn't work:

run a simple test

cd adaptive/tests/
python test_simple.py

1. The directory name is wrong. It should be 'adaptivemd/tests/'
2. The MongoDB database has to be running, which is not mentioned.
3. It generates an assertion error:

(python2) macbook>python ./test_simple.py
changed state to booting
changed state to running
task succeeded
re