by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Daniel Wheeler
    @wd15
    asdf #Test
    asdf # test

    test

    stuff

    test

    Trevor Keller
    @tkphd
    Yep, that's working.
    Trevor Keller
    @tkphd
    The CHiMaD workflow (@wd15 creates, @tkphd reviews, @wd15 merges) has thrown things off for me. @guyer, for #541, #542, #543, once requested reviews have passed, would you like one of us to merge your PR? Or does the inclusion of a code-review cycle imply a CHiMaD-esque workflow?
    Trevor Keller
    @tkphd
    Due to the lapse in funding and subsequent shutdown of our government, the Federal employees among us (@guyer, @tkphd, @wd15) are furloughed, and the website is likely to go down until funding is restored. We will respond to open discussions after NIST re-opens for business.
    Trevor Keller
    @tkphd
    ... and we're back :smiley:
    Raghavendra Saralaya
    @numoonchld
    can this package be used to obtain solutions for simple 2nd order PDE - i.e. classical wave equations?
    symbolic solutions not numberical
    *numerical
    Raghavendra Saralaya
    @numoonchld
    i guess this is purely numerical
    Daniel Wheeler
    @wd15
    Right, FiPy is only numerical using the finite volume method.
    Yuri de Abreu
    @yurigba

    I am trying to run fipy from source, but when I run the program testFiPy.py in vscode I get a NameError:

    PYDEV DEBUGGER WARNING:
    sys.settrace() should not be used when the debugger is being used.
    This may cause the debugger to stop working correctly.
    If this is needed, please check:
    http://pydev.blogspot.com/2007/06/why-cant-pydev-debugger-work-with.html
    to see how to restore the debug tracing back correctly.
    Call Location:
      File "C:\Users\Yuri\anaconda3\envs\clifipy\lib\doctest.py", line 1480, in run
        sys.settrace(save_trace)
    
    .............................................................................<frozen importlib._bootstrap>:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
    .............C:\Users\Yuri\anaconda3\envs\clifipy\lib\site-packages\scipy\sparse\_index.py:126: SparseEfficiencyWarning: Changing the sparsity structure of a csr_matrix is expensive. lil_matrix is more efficient.
      self._set_arrayXarray(i, j, x)
    ..
    ======================================================================
    ERROR: import solvers.test
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "C:\Users\Yuri\Documents\GitHub\clifipy\fipy\tests\lateImportTest.py", line 21, in setUp
        module = __import__(self.moduleName)
      File "c:\Users\Yuri\Documents\GitHub\clifipy\fipy\solvers\__init__.py", line 8, in <module>
        __all__ = list(solver.__all__)
    NameError: name 'solver' is not defined
    
    ======================================================================
    ERROR: import terms.test
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "C:\Users\Yuri\Documents\GitHub\clifipy\fipy\tests\lateImportTest.py", line 21, in setUp
        module = __import__(self.moduleName)
      File "c:\Users\Yuri\Documents\GitHub\clifipy\fipy\terms\__init__.py", line 64, in <module>
        __all__.extend(transientTerm.__all__)
    NameError: name 'transientTerm' is not defined

    What could be this problem?

    Daniel Wheeler
    @wd15
    What happens when your run python -c "import fipy"?
    Yuri de Abreu
    @yurigba
    It loads, without complaining of anything
    I'm using Python 3.8.2, I think this is relevant
    Daniel Wheeler
    @wd15
    I think you'll need to try and debug vscode and understand it. Try looking at fipy.__file__ or fipy.__path__ maybe.
    Yuri de Abreu
    @yurigba
    Well, I have made some progress, I am now using fipy, but I'd like to know if it is possible to use the fipy.terms.explicitDiffusionTerm but instead of stepping over the same variable, step over other variable... something like a staggered mesh scheme
    Daniel Wheeler
    @wd15
    That's possible. Probably best to try and implement something and then ask a very specific question on Stackoverflow using the fipy tag and provide code that you tried to use to implement the problem.
    Yuri de Abreu
    @yurigba
    Good idea. Thanks for the advice.